How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Full methodology →
Signals refreshed2026-06-22 00:01 UTC·Repo last pushed 58 days ago
Rank Trend
2026-06-202026-06-21
Activity & Reach
Stars
8.3k
Forks
641
Last Push
2026-04-25
58 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
9
Rank Change
=
was #288
Analysis
HVTrust Dimensions
19.6 / 100 · 50.0% confidence
Safety / IntegrityOSSF, provenance, signatures
2.5 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
8.5 / 17
MaintenanceFreshness and commits
8.1 / 20
AdoptionStars and downloads
9.4 / 20
Activity Inputs
53.8 / 100
StarsRepository reach
23.5 / 30
FreshnessLast push recency
16.9 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
13.1 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
49%
of last 100 commits verified
Is MiroThinker safe?
Public trust evidence for MiroThinker is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does MiroThinker publish package provenance?
No published build provenance is currently detected for MiroThinker. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does MiroThinker have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for MiroThinker. 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 MiroThinker actively maintained?
Slowing down. Last push was 58 days ago — keep an eye on whether activity resumes.
What license does MiroThinker use?
MiroThinker ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MiroThinker's commits signed?
49% of the last 100 commits to MiroThinker 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.
AI agent surface
Profile context only
HVTrust currently ranks supply-chain and project-integrity trust only. This public view shows a compact AI-agent surface snapshot from repo docs and manifests. These fields are descriptive context and do not affect the production HVTrust rank. An experimental local preview remains available in Score Lab →, and the policy boundary is tracked on the roadmap →
MCP Server Support
high confidence
Implemented
MiroThinker appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
5 detected
Public provider/service dependencies detected.
Anthropic
E2B
Google Gemini
OpenAI
Redis
Credential signal:
API keys or service config markers documented.
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
N/A
No package source configured
Detailed evidence is not shown in the public view.
MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live
Maintain MiroThinker?
HVTrust scores MiroThinker 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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.2 · Raw JSON
