How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Full methodology →
Signals refreshed2026-06-22 00:01 UTC·Repo last pushed 77 days ago
Rank Trend
2026-06-202026-06-21
Activity & Reach
Stars
3.4k
Forks
312
Last Push
2026-04-06
77 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
35
Rank Change
=
was #201
Analysis
HVTrust Dimensions
45.6 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
8.3 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
11.1 / 17
MaintenanceFreshness and commits
6.9 / 20
AdoptionStars and downloads
8.5 / 20
Activity Inputs
47.5 / 100
StarsRepository reach
21.2 / 30
FreshnessLast push recency
14.3 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
11.6 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
3.1 / 10
OpenSSF Scorecard · scanned Jun 21, 2026
Signed Commits
88%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection5
CI-Tests0
CII-Best-Practices0
Code-Review2
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool0
Fuzzing0
License10
Maintained1
Packaging-1
Pinned-Dependencies0
SAST0
Security-Policy0
Signed-Releases-1
Token-Permissions0
Vulnerabilities0
Is Srcbook safe?
Public trust evidence for Srcbook is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Srcbook publish package provenance?
No published build provenance is currently detected for Srcbook. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Srcbook have an OpenSSF Scorecard?
Srcbook has an OpenSSF Scorecard score of 3.1/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Srcbook actively maintained?
Slowing down. Last push was 77 days ago — keep an eye on whether activity resumes.
What license does Srcbook use?
Srcbook ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Srcbook's commits signed?
88% of the last 100 commits to Srcbook are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
Profile context only
HVTrust currently ranks supply-chain and project-integrity trust only. This public view shows a compact AI-agent surface snapshot from repo docs and manifests. These fields are descriptive context and do not affect the production HVTrust rank. An experimental local preview remains available in Score Lab →, and the policy boundary is tracked on the roadmap →
MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Anthropic
OpenAI
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
1 tags
Broad capability areas detected.
code
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live
Maintain Srcbook?
HVTrust scores Srcbook from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.2 · Raw JSON
