Home/parlant/Trust report

Trust and health report

parlant - 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.

Steady60% signal

last push 38d ago · last release 3mo

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

Provenance

Repository identity and fork provenance (github_public_v1).

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
1mo
Scanner
osv@v1
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

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/emcie-co-parlant/trust.

Common questions

Is parlant maintained?
GraphCanon rates parlant "Steady" (60% maintenance signal from public GitHub metadata, computed today). Last push was 38 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
Is parlant safe to use?
Last scanned 1mo (mcp_manifest profile). Status: 2 low - 2 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 parlant as safe - review maintenance, provenance, and scan findings on this page before adopting.
Is parlant a fork?
No. parlant is not flagged as a fork in GitHub metadata at the time of the last refresh.
Does parlant have known security vulnerabilities?
Last scanned 1mo (mcp_manifest profile). Status: 2 low - 2 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 parlant 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 parlant?
We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for parlant. Signals are sourced heuristics with explicit limits - see trust methodology.
How does GraphCanon assess trust for parlant?
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.