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 yesterday
Activity & Reach
Stars
1.6k
Forks
203
Last Push
2026-06-21
yesterday
Commits (4 wk)
43
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
223
Rank Change
=
was #262
Analysis
HVTrust Dimensions
24.6 / 100 · 50.0% confidence
Safety / IntegrityOSSF, provenance, signatures
3.6 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
8.5 / 17
MaintenanceFreshness and commits
18.5 / 20
AdoptionStars and downloads
7.7 / 20
Activity Inputs
75.4 / 100
StarsRepository reach
19.2 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
20.5 / 25
CommunityFork signal
10.7 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
73%
of last 100 commits verified
Is Golem safe?
Source-available software. A lower HVTrust score reflects fewer public supply-chain artifacts (open license, build provenance, signed commits) — not a security finding. Golem may have internal security practices not visible through public signals.
Public trust evidence for Golem 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 Golem publish package provenance?
No published build provenance is currently detected for Golem. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Golem have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Golem. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Golem actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Golem use?
Golem ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Golem's commits signed?
73% of the last 100 commits to Golem 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
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface 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 Golem?
HVTrust scores Golem 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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.2 · Raw JSON
