Trust and health report
better-chatbot - 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 33d ago
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 965636860
- Not a fork
- Verified publisher: organization 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
No lockfile (source not queried)- Last query
- today
- Scanner
- osv@v1
OpenSSF Scorecard
Not queried- Scanner
- openssf-scorecard@v1
Weekly public scans omit some checks at scale.
View source evidenceMethod 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/keinsaasforever-better-chatbot/trust.
Common questions
- Is better-chatbot maintained?
- GraphCanon rates better-chatbot "Steady" (60% maintenance signal from public GitHub metadata, computed today). Last push was 33 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is better-chatbot safe to use?
- Last scanned today (mcp_manifest profile). Status: No MCP manifest. Absence of findings in our scan is not a security guarantee - see trust methodology for scope limits. GraphCanon does not certify better-chatbot as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is better-chatbot a fork?
- No. better-chatbot is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does better-chatbot have known security vulnerabilities?
- Last scanned today (mcp_manifest profile). Status: No MCP manifest. Absence of findings in our scan is not a security guarantee - see trust methodology for scope limits.
- How often is the better-chatbot 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 better-chatbot?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for better-chatbot. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for better-chatbot?
- 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.