Home/pro-workflow/Trust report

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 Oct 26, 2026 · GitHub synced Oct 26, 2026

Maintenance

Snapshot computed Oct 26, 2026

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

Active82% signal

last push 26d before snapshot · last release Sep 28, 2026 · 1 releases (90d)

+59 stars (30d) · +3 open issues (30d)

Provenance

Repository identity and fork provenance (github_public_v1).

  • GitHub repo id: 1147470802
  • Not a fork
  • Personal account
  • Computed Oct 26, 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

Published findings
Last query
Jul 15, 2026
Scanner
osv@v1
Published findings
1
View source evidence

deps.dev advisories

Not queried
Scanner
deps.dev@v1
View source evidence

OpenSSF Scorecard

Not queried
Scanner
openssf-scorecard@v1

Weekly public scans omit some checks at scale.

View source evidence

Dependency advisories (deduplicated)

GHSA-g7r4-m6w7-qqqr
esbuild@0.28.0 · osv@v1
package-lock.json

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 "Active" (82% maintenance signal from public GitHub metadata, computed Oct 26, 2026). At that snapshot, the last push was 26 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 pro-workflow safe to use?
Last scanned Jul 15, 2026 (deps profile). Published findings: 1 low. 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 Jul 15, 2026 (deps profile). Published findings: 1 low. 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 Oct 26, 2026 (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.

Was this helpful?

Anonymous feedback helps us improve pages and translations.