◆ Compliance Automation & Trust Management

Strike Graph

commercial

Summary

Strike Graph is a commercial compliance-automation platform that helps companies build, manage, and automate their compliance programs to achieve certifications like SOC 2 and ISO 27001. It is not specified how it is run, but it is for compliance owners, and its documentation positions it alongside audit-readiness tooling. The project was launched in 2020 and has seen 14 releases in the window we track, with the last release occurring 19 days ago.

How Strike Graph helps

Which of our controls have no evidence attached before the auditor asks for it?

flags controls lacking linked evidence and shows the gap by control, before it becomes an audit finding

Which security requirements from SOC 2 and ISO 27001 overlap, so we are not doing the same work twice?

maps controls across both frameworks and shows where one piece of evidence satisfies requirements in each

Which policies are overdue for review or missing an owner's sign-off?

tracks each policy's review cycle and approval status and lists the ones past due

Are we actually ready for the audit, or still guessing?

rolls up control status across the whole program into a readiness view so gaps show up before the auditor finds them

Which employees haven't completed the training or acknowledgments our certification requires?

tracks completion per employee against the required set and lists who is outstanding

Languages

Not documented

Score card

Shipping velocity releases a month, last 12 months
Documentation quality release-notes rubric, 0–100
Breaking-change discipline how rarely a release breaks users, and notice given
Maintenance risk quiet time against its own cadence, maintainers
Innovation & surface new capabilities, API and MCP surface

Five scores for Strike Graph, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored

Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
Documentation quality — the release-notes rubric published on the analytics page, unchanged.
Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail Strike Graph puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →