Skip to content

Guidance Software, Inc.: filings

Every Guidance Software, Inc. annual and quarterly report in the SEC record with the published financial measures it tagged, 25 filings, each linked to its SEC index.

Filing record ends 2017-08-07

The latest filing in this captured record is a 10-Q filed 2017-08-07. No later filing is in the SEC companyfacts record captured on 2026-09-22. Guidance Software, Inc. may have stopped filing, merged, or changed its reporting entity; nothing on this page describes its current status. Values are as reported at the time.

Filings with published measures

Each page shows what one filing reported, as tagged in that filing, with the periods it covered. Later filings can restate a value; the company overview shows the latest-filed value per period.

FormFiledFiscal periodMeasuresFactsSEC accession
10-Q2017-08-07fiscal Q2 2017461310001104659-17-049926
10-Q2017-05-10fiscal Q1 201742850001104659-17-031548
10-K2017-03-01fiscal FY 2016452160001104659-17-013038
10-Q2016-11-08fiscal Q3 2016421230001104659-16-155559
10-Q2016-08-05fiscal Q2 2016421230001104659-16-137643
10-Q2016-05-06fiscal Q1 201641830001104659-16-118795
10-K2016-02-25fiscal FY 2015452080001104659-16-099794
10-Q2015-11-06fiscal Q3 2015421210001104659-15-076761
10-Q2015-08-05fiscal Q2 2015421210001104659-15-056562
10-Q2015-05-08fiscal Q1 201542850001104659-15-036288
10-K2015-02-24fiscal FY 2014452090001104659-15-013463
10-Q2014-11-12fiscal Q3 2014421210001104659-14-079854
10-Q2014-08-08fiscal Q2 2014421210001104659-14-058925
10-Q2014-05-08fiscal Q1 201442850001104659-14-036580
10-K2014-02-24fiscal FY 2013452090001104659-14-012776
10-Q2013-11-08fiscal Q3 2013421210001104659-13-082842
10-Q2013-08-08fiscal Q2 2013401150001104659-13-061744
10-Q2013-05-08fiscal Q1 201340810001104659-13-038930
10-K2013-02-21fiscal FY 2012432050001104659-13-012759
10-Q2012-11-02fiscal Q3 2012401170001104659-12-073692
10-Q2012-08-03fiscal Q2 2012401160001104659-12-054155
10-Q2012-05-15fiscal Q1 201236740001104659-12-037520
10-K2012-02-16fiscal FY 201135930001104659-12-010611
10-Q2011-11-03fiscal Q3 2011371060001104659-11-060597
10-Q2011-08-04fiscal Q2 2011401110001104659-11-043756

Inspect the source

Entity
Guidance Software, Inc. / CIK 0001375557
Captured
SEC response SHA-256
601f5682860b3dcfe12ae4a3d452f211f7f8bacc35bf0f86ee13a55e6a1483ab

Current SEC company facts · Download the original response snapshot (gzip) · Download the selected JSON

Every published concept a filing tagged, with the periods it covered, as reported in that filing at capture time. Forms 10-K, 10-K/A, 10-Q, 10-Q/A, 20-F, 20-F/A, 40-F, 40-F/A. A filing page needs at least 8 published concepts. Later filings can restate these values; the company history pages show the latest-filed value per period.

Public company accounting reference, not market prices, returns, an investment recommendation, or ALPHAC performance. Validate a separately constructed return series with the validation API; accounting values are not returns.

Use this in research

A financial period ends before its results become public. Use the filing date as a minimum availability boundary, inspect amendments, and retain the original filing vintage when testing historical signals. This latest-filed selection can contain information unavailable at the time.

These pages do not supply prices, total-return histories, corporate-action adjustments or a tradable universe. Build those inputs separately before evaluating a strategy. A profitable backtest can still reflect selection bias or costs that were left out.

Research methodology · Execution and cost assumptions · Check backtest overfitting

Build with the open-source tools

Use these accounting records as inspectable inputs. When you have constructed a return series, the validation tools can help test its statistical evidence and preserve the result with its limitations.

Read the published dataset with Python
import json
from urllib.request import urlopen

with urlopen("https://canlicapital.com/company-data/0001375557.json") as response:
    record = json.load(response)
print(record["fetched_at"])
print(record["policy"])
for concept in record["concepts"]:
    print(concept["tag"], next(iter(concept["observations"])))