Mirascope

The LLM Anti-Framework

Agent Frameworks Python Grade D Listed MIT
48.5/100
Rank #971 of 1328
Compare Mirascope

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-09-13 · 7d ago
Recent change
No recent signal change

Is Mirascope safe? Mirascope scores 48.5/100 (Grade D), ranked #971 of 1328 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.6/10; 3% of recent commits are signed; last pushed 2026-09-13. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-12
Rank Moved
Rank dropped 10 spots (#953 → #963)
2026-09-11
Rank Moved
Rank dropped 11 spots (#942 → #953)
2026-09-09
Rank Moved
Rank dropped 15 spots (#919 → #934)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.6/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
65.0
Activity sub-score · out of 100
#83

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. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-20 15:32 UTC · Repo last pushed 7 days ago

Rank Trend

2026-08-11 2026-09-20

Activity & Reach

Stars
1.5k
Forks
127
Last Push
2026-09-13
7 days ago
Commits (4 wk)
8?
Downloads (7d)
HN mentions (30d)
Open Issues
11
Rank Change
▼6
was #965

Analysis

HVTrust Dimensions vs Agent Frameworks

48.5 / 100 · 100.0% confidence

Mirascope Agent Frameworks average (122 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.9 / 25
3.8 below avg 9.7
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
12.4 / 17
in line with avg 12.4
Maintenance60% last-push freshness · 40% commit activity
13.4 / 20
in line with avg 13.9
AdoptionLog-scaled stars · package downloads
7.6 / 20
3.6 below avg 11.2

Activity Inputs

65.0 / 100
StarsRepository reach
19.1 / 30
FreshnessLast push recency
24.0 / 25
ActivityRecent commits
11.9 / 25
CommunityFork signal
9.8 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.6 / 10
OpenSSF Scorecard · scanned Sep 19, 2026
Signed Commits
3%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 5
CI-Tests -1
CII-Best-Practices 0
Code-Review 0
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Is Mirascope safe?

Public trust evidence for Mirascope 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 Mirascope publish package provenance?
No published build provenance is currently detected for Mirascope. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Mirascope have an OpenSSF Scorecard?
Mirascope has an OpenSSF Scorecard score of 4.6/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 Mirascope actively maintained?
Actively maintained. The repository was pushed to within the last 7 day(s).
What license does Mirascope use?
Mirascope ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Mirascope's commits signed?
3% of the last 100 commits to Mirascope 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

MCP, providers, tool surface
Scored in HVTrust

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 → Compare this surface across every listed agent in the capability matrix →

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
3 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
Extensions
Extension based plugin/integration surface detected.
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 Mirascope?

For maintainers

HVTrust scores Mirascope 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.

Reputation Timeline

Signal history
Rank 26Grade 6HVTrust 1Scorecard 1
2026-09-12
Rank Moved
Rank dropped 10 spots (#953 → #963)
2026-09-11
Rank Moved
Rank dropped 11 spots (#942 → #953)
2026-09-09
Rank Moved
Rank dropped 15 spots (#919 → #934)
2026-09-07
Rank Moved
Rank dropped 38 spots (#879 → #917)
2026-09-06
Rank Moved
Rank dropped 14 spots (#865 → #879)
2026-09-05
Rank Moved
Rank dropped 58 spots (#807 → #865)
2026-09-04
Rank Moved
Rank dropped 30 spots (#777 → #807)
2026-09-03
Rank Moved
Rank dropped 67 spots (#710 → #777)
2026-09-02
Rank Moved
Rank dropped 37 spots (#673 → #710)
2026-09-01
Grade Changed
Trust grade C → D
2026-09-01
Rank Moved
Rank dropped 25 spots (#648 → #673)
2026-08-31
Rank Moved
Rank dropped 35 spots (#613 → #648)
2026-08-30
Rank Moved
Rank dropped 12 spots (#601 → #613)
2026-08-29
Grade Changed
Trust grade D → C
2026-08-29
Rank Moved
Rank dropped 31 spots (#570 → #601)
2026-08-27
Rank Moved
Rank dropped 17 spots (#544 → #561)
2026-08-26
Rank Moved
Rank dropped 79 spots (#465 → #544)
2026-08-24
Rank Moved
Rank dropped 14 spots (#451 → #465)
2026-08-22
Grade Changed
Trust grade C → D
2026-08-22
Rank Moved
Rank rose 10 spots (#462 → #452)
2026-08-19
Grade Changed
Trust grade D → C
2026-08-18
Grade Changed
Trust grade C → D
2026-08-17
Rank Moved
Rank rose 11 spots (#461 → #450)
2026-08-13
Rank Moved
Rank dropped 17 spots (#431 → #448)
2026-08-12
Rank Moved
Rank rose 12 spots (#443 → #431)
2026-08-10
Rank Moved
Rank dropped 17 spots (#434 → #451)
2026-08-08
Rank Moved
Rank dropped 110 spots (#319 → #429)
2026-07-15
Rank Moved
Rank dropped 18 spots (#263 → #281)
2026-07-14
Rank Moved
Rank dropped 14 spots (#249 → #263)
2026-07-13
Rank Moved
Rank dropped 29 spots (#220 → #249)
2026-06-24
Scorecard Added
OSSF Scorecard: 4.6/10
2026-06-24
Grade Changed
Trust grade D → C
2026-06-24
Rank Moved
Rank rose 81 spots (#293 → #212)
2026-06-24
HVTrust Changed
HVTrust up 32.1pts (21.9 → 54.0)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 48.5 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/mirascope.svg)](https://hvtracker.net/agents/mirascope)
HTML:
<a href="https://hvtracker.net/agents/mirascope"><img src="https://hvtracker.net/badge/mirascope.svg" alt="HVTrust"></a>

Other agents in Agent Frameworks

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON