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:11 UTC·Repo last pushed 6 days ago
Rank Trend
2026-06-022026-06-04
Activity & Reach
Stars
19.2k
Forks
2.0k
Last Push
2026-05-29
6 days ago
Commits (4 wk)
2?
Downloads (7d)
2,552
pypi
HN mentions (30d)
2
Open Issues
207
Rank Change
▲55
was #93
Analysis
HVTrust Dimensions
76.9 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
17.9 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
13.6 / 17
MaintenanceFreshness and commits
12.6 / 20
AdoptionStars and downloads
14.8 / 20
Activity Inputs
71.2 / 100
StarsRepository reach
25.7 / 30
FreshnessLast push recency
24.2 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
15.3 / 20
Supply Chain Trust
Package Provenance
Verified
pypi attestation
OSSF Scorecard
6.0 / 10
via deps.dev · OpenSSF
Signed Commits
59%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection6
CI-Tests10
CII-Best-Practices0
Code-Review5
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License10
Maintained10
Packaging10
Pinned-Dependencies0
SAST10
Security-Policy10
Signed-Releases0
Token-Permissions0
Vulnerabilities0
Is Taipy safe?
Public supply-chain signals for Taipy are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Taipy carries less obvious unverified-evidence risk than projects with thin signals.
Does Taipy publish package provenance?
Yes. Taipy's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Taipy have an OpenSSF Scorecard?
Taipy has an OpenSSF Scorecard score of 6.0/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 Taipy actively maintained?
Actively maintained. The repository was pushed to within the last 6 day(s).
What license does Taipy use?
Taipy ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Taipy's commits signed?
59% of the last 100 commits to Taipy 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.
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 Taipy?
HVTrust scores Taipy 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.
