How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Full methodology →
Signals refreshed2026-06-04 00:07 UTC·Repo last pushed 14 days ago
Rank Trend
2026-06-012026-06-03
Activity & Reach
Stars
12.3k
Forks
671
Last Push
2026-05-21
14 days ago
Commits (4 wk)
7
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
21
Rank Change
▼3
was #112
Analysis
HVTrust Dimensions
59.6 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
10.3 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
14.0 / 17
MaintenanceFreshness and commits
14.7 / 20
AdoptionStars and downloads
9.8 / 20
Activity Inputs
72.2 / 100
StarsRepository reach
24.5 / 30
FreshnessLast push recency
23.1 / 25
ActivityRecent commits
11.3 / 25
CommunityFork signal
13.1 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
6.5 / 10
via deps.dev · OpenSSF
Signed Commits
43%
of last 100 commits verified
Code-Review10
Maintained10
Security-Policy10
Dangerous-Workflow10
CII-Best-Practices0
Token-Permissions0
Binary-Artifacts10
Fuzzing0
License10
Branch-Protection-1
Signed-Releases0
Packaging10
Pinned-Dependencies1
SAST9
Is Infracost safe?
Infracost has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Infracost publish package provenance?
No published build provenance is currently detected for Infracost. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Infracost have an OpenSSF Scorecard?
Infracost has an OpenSSF Scorecard score of 6.5/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 Infracost actively maintained?
Maintained. Last push was 14 days ago.
What license does Infracost use?
Infracost ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Infracost's commits signed?
43% of the last 100 commits to Infracost 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.
Runtime trust — coming soon
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
Maintain Infracost?
HVTrust scores Infracost 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) · OSSF Scorecard via deps.dev
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.1 · Raw JSON
