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 yesterday
Rank Trend
2026-05-252026-06-04
Activity & Reach
Stars
2.5k
Forks
235
Last Push
2026-06-03
yesterday
Commits (4 wk)
12
Downloads (7d)
5,770
pypi
HN mentions (30d)
0
Open Issues
72
Rank Change
▼4
was #78
Analysis
HVTrust Dimensions
67.2 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
12.9 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
13.9 / 17
MaintenanceFreshness and commits
16.4 / 20
AdoptionStars and downloads
13.2 / 20
Activity Inputs
70.3 / 100
StarsRepository reach
20.4 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
13.9 / 25
CommunityFork signal
11.0 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
6.3 / 10
via deps.dev · OpenSSF
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection8
CI-Tests10
CII-Best-Practices0
Code-Review10
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License10
Maintained10
Packaging-1
Pinned-Dependencies0
SAST9
Security-Policy0
Signed-Releases-1
Token-Permissions0
Vulnerabilities0
Is Griptape safe?
Griptape 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 Griptape publish package provenance?
No published build provenance is currently detected for Griptape. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Griptape have an OpenSSF Scorecard?
Griptape has an OpenSSF Scorecard score of 6.3/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 Griptape actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Griptape use?
Griptape ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Griptape's commits signed?
100% of the last 100 commits to Griptape 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 Griptape?
HVTrust scores Griptape 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.
