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. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Signals refreshed2026-07-07 22:30 UTC·Repo last pushed 8 days ago
Activity & Reach
Stars
5.0k
Forks
267
Last Push
2026-06-29
8 days ago
Commits (4 wk)
9
Downloads (7d)
11,564
pypi
HN mentions (30d)
—
Open Issues
19
Rank Change
NEW
Analysis
HVTrust Dimensions
68.9 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
11.6 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
8.5 / 17
MaintenanceFreshness and commits
15.5 / 20
AdoptionStars and downloads
14.3 / 20
Activity Inputs
69.9 / 100
StarsRepository reach
22.2 / 30
FreshnessLast push recency
23.9 / 25
ActivityRecent commits
12.5 / 25
CommunityFork signal
11.3 / 20
Supply Chain Trust
Package Provenance
Verified
pypi attestation
OSSF Scorecard
—
Not available
Signed Commits
81%
of last 100 commits verified
Is Solace Agent Mesh safe?
Solace Agent Mesh 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 Solace Agent Mesh publish package provenance?
Yes. Solace Agent Mesh's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Solace Agent Mesh have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Solace Agent Mesh. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Solace Agent Mesh actively maintained?
Maintained. Last push was 8 days ago.
What license does Solace Agent Mesh use?
Solace Agent Mesh ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Solace Agent Mesh's commits signed?
81% of the last 100 commits to Solace Agent Mesh 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.
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology →
MCP Server Support
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
4 detected
Public provider/service dependencies detected.
Amazon Bedrock
OpenAI
Postgres
Tavily
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
browser
code
database
search
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live
Maintain Solace Agent Mesh?
HVTrust scores Solace Agent Mesh 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.
