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 20:15 UTC·Repo last pushed 2 days ago
Rank Trend
2026-05-242026-06-04
Activity & Reach
Stars
9.9k
Forks
2.2k
Last Push
2026-06-02
2 days ago
Commits (4 wk)
30
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
291
Rank Change
▼9
was #110
Analysis
HVTrust Dimensions
60.8 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
10.1 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
12.5 / 17
MaintenanceFreshness and commits
17.8 / 20
AdoptionStars and downloads
9.6 / 20
Activity Inputs
83.0 / 100
StarsRepository reach
24.0 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
18.6 / 25
CommunityFork signal
15.5 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
4.7 / 10
via deps.dev · OpenSSF
Signed Commits
84%
of last 100 commits verified
Binary-Artifacts9
Branch-Protection0
CI-Tests10
CII-Best-Practices0
Code-Review8
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool0
Fuzzing0
License10
Maintained10
Packaging-1
Pinned-Dependencies2
SAST1
Security-Policy9
Signed-Releases-1
Token-Permissions0
Vulnerabilities0
Is Spring AI Alibaba safe?
Spring AI Alibaba 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 Spring AI Alibaba publish package provenance?
No published build provenance is currently detected for Spring AI Alibaba. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Spring AI Alibaba have an OpenSSF Scorecard?
Spring AI Alibaba has an OpenSSF Scorecard score of 4.7/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 Spring AI Alibaba actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does Spring AI Alibaba use?
Spring AI Alibaba ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Spring AI Alibaba's commits signed?
84% of the last 100 commits to Spring AI Alibaba 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 Spring AI Alibaba?
HVTrust scores Spring AI Alibaba 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
