Home/SpiffWorkflow/Trust report

Trust and health report

SpiffWorkflow - trust report

Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.

GraphCanon updated Oct 27, 2026 · GitHub synced Oct 27, 2026

Maintenance

Snapshot computed Oct 27, 2026

Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.

Active82% signal

last push 14d before snapshot · last release Aug 10, 2026 · 1 releases (90d)

+12 stars (30d) · 0 open issues (30d)

Provenance

Repository identity and fork provenance (github_public_v1).

  • GitHub repo id: 448831
  • Not a fork
  • GitHub organization account
  • Computed Oct 27, 2026

Security intelligence

Source-by-source security scan results from public intelligence providers. Missing, partial, or failed queries are shown explicitly and are not treated as clean.

OSV dependency advisories

No lockfile (source not queried)
Last query
Jul 15, 2026
Scanner
osv@v1
View source evidence

deps.dev advisories

No lockfile (source not queried)
Last query
Aug 2, 2026
Scanner
deps.dev@v1
View source evidence

OpenSSF Scorecard

Published findings; additional observations pending review
Last query
Jul 26, 2026
Scanner
openssf-scorecard@v1
Published findings
1

Weekly public scans omit some checks at scale.

View source evidence

OpenSSF Scorecard checks

Code-Review (4/10): Found 8/19 approved changesets -- score normalized to 4
https://github.com/ossf/scorecard/blob/64febf8c5229a2a65d09c6b543677b28a51abb09/docs/checks.md#code-review

Method and caveats: these are sourced, dated heuristics from public GitHub data and external security intelligence providers. A status like "no published findings from this source" is not a guarantee of safety. Read the full trust methodology · JSON report at /api/graphcanon/tools/sartography-spiffworkflow/trust.

Common questions

Is SpiffWorkflow maintained?
GraphCanon rates SpiffWorkflow "Active" (82% maintenance signal from public GitHub metadata, computed Oct 27, 2026). At that snapshot, the last push was 14 days earlier. 1 GitHub releases in the 90 days preceding that snapshot. This is a recency heuristic, not a guarantee the project will stay maintained.
Is SpiffWorkflow safe to use?
Last scanned Aug 2, 2026 (deps_dev profile). Status: No lockfile. Absence of findings in our scan is not a security guarantee - see trust methodology for scope limits. GraphCanon does not certify SpiffWorkflow as safe - review maintenance, provenance, and scan findings on this page before adopting.
Is SpiffWorkflow a fork?
No. SpiffWorkflow is not flagged as a fork in GitHub metadata at the time of the last refresh.
Does SpiffWorkflow have known security vulnerabilities?
Last scanned Aug 2, 2026 (deps_dev profile). Status: No lockfile. Absence of findings in our scan is not a security guarantee - see trust methodology for scope limits.
How often is the SpiffWorkflow trust report updated?
Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed Oct 27, 2026 (methodology github_public_v1).
What does GraphCanon never claim about SpiffWorkflow?
We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for SpiffWorkflow. Signals are sourced heuristics with explicit limits - see trust methodology.
How does GraphCanon assess trust for SpiffWorkflow?
Signals are sourced from public GitHub metadata and optional dependency/MCP manifest scans, each tagged with methodology version and computed date. GraphCanon does not publish a composite safety grade. Read trust methodology for full scope and limits.

Was this helpful?

Anonymous feedback helps us improve pages and translations.