Trust and health report
pro-workflow - trust report
Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.
GraphCanon updated today · GitHub synced today
Maintenance
Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.
last push 1d ago · last release 2mo · 1 releases (90d)
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 1147470802
- Not a fork
- Personal account
- Computed today
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
Published findings- Last query
- today
- Scanner
- osv@v1
- Stored findings
- 1
OpenSSF Scorecard
Not queried- Scanner
- openssf-scorecard@v1
Weekly public scans omit some checks at scale.
View source evidenceDependency advisories (deduplicated)
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/rohitg00-pro-workflow/trust.
Common questions
- Is pro-workflow maintained?
- GraphCanon rates pro-workflow "Very active" (96% maintenance signal from public GitHub metadata, computed today). Last push was 1 days ago. 1 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is pro-workflow safe to use?
- Last scanned today (deps profile). Status: 1 low - 1 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report. GraphCanon does not certify pro-workflow as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is pro-workflow a fork?
- No. pro-workflow is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does pro-workflow have known security vulnerabilities?
- Last scanned today (deps profile). Status: 1 low - 1 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report.
- How often is the pro-workflow trust report updated?
- Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed today (methodology github_public_v1).
- What does GraphCanon never claim about pro-workflow?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for pro-workflow. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for pro-workflow?
- 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.