@gitlawb/openclaude logo

@gitlawb/openclaude

#1709 · by gitlawb
2.99/ 5.00
cautionBeta
May 12, 2026 at 6:06 PM6 signals analysedNo manual reviews · fully automated
Trust Signal Breakdown
unverified3 sub-signals across 6 dimensions

CVEs, dependency health, and supply chain integrity

1 of 3 sub-signals with data

Known CVEs100%4.8

2 CVE(s) found — 0 unpatched

via OSV.dev

Dependency Healthno data

Weight redistributed to sub-signals with data

Supply Chainno data

Weight redistributed to sub-signals with data

Uptime, latency, error rates, and incident history

0 of 0 sub-signals with data

Commit recency, release cadence, issue response, CI/CD

0 of 0 sub-signals with data

Downloads, stars, dependents, and growth trajectory

0 of 0 sub-signals with data

License, documentation, security policy, changelog

0 of 0 sub-signals with data

Track record, org maturity, community standing

0 of 0 sub-signals with data

About this score
Scored across 3 sub-signals in 6 dimensionsScoring engine v1 (beta) — actively being expandedPhase 1: Core sub-signal architecture (live)Phase 2: Permission scope & expanded collection (in progress)
Trust AssessmentAI Assessment

Claude Code opened to any LLM — OpenAI, Gemini, DeepSeek, Ollama, and 200+ models

Incidents & Alertslast 90 days
May 12@gitlawb/openclaude added to Trust Index2.99
Showing 1 of 1 events
Score History4 snapshots
5.003.752.501.250.00
May 12May 12
Data Sources6 indexed

Are you the publisher?

Claim this profile to unlock deeper evaluation, real-time monitoring,
and trust signals that help agents discover your service.

Share this Trust Score

Generate a scorecard image optimised for X, LinkedIn and other social platforms.

⬇ Download Score Card