How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Full methodology →
Signals refreshed2026-06-04 20:15 UTC·Repo last pushed today
Rank Trend
2026-05-252026-06-04
Activity & Reach
Stars
5.4k
Forks
468
Last Push
2026-06-04
today
Commits (4 wk)
72
Downloads (7d)
5,196
pypi
HN mentions (30d)
2
Open Issues
67
Rank Change
▼2
was #60
Analysis
HVTrust Dimensions
71.0 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
12.6 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
14.3 / 17
MaintenanceFreshness and commits
19.4 / 20
AdoptionStars and downloads
13.9 / 20
Activity Inputs
83.0 / 100
StarsRepository reach
22.4 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
23.2 / 25
CommunityFork signal
12.4 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
6.8 / 10
via deps.dev · OpenSSF
Signed Commits
82%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection8
CI-Tests10
CII-Best-Practices0
Code-Review4
Contributors10
Dangerous-Workflow0
Dependency-Update-Tool10
Fuzzing0
License10
Maintained10
Packaging-1
Pinned-Dependencies10
SAST9
Security-Policy10
Signed-Releases0
Token-Permissions10
Vulnerabilities10
Is Giskard safe?
Giskard 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 Giskard publish package provenance?
No published build provenance is currently detected for Giskard. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Giskard have an OpenSSF Scorecard?
Giskard has an OpenSSF Scorecard score of 6.8/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 Giskard actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Giskard use?
Giskard ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Giskard's commits signed?
82% of the last 100 commits to Giskard 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 Giskard?
HVTrust scores Giskard 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.
