Magentic

Seamlessly integrate LLMs as Python functions

Agent Frameworks Python Grade D Listed MIT
37.8/100
Rank #385 of 468
Compare Magentic

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-03-11 · 148d ago
Recent change
No recent signal change

Is Magentic safe? Magentic scores 37.8/100 (Grade D), ranked #385 of 468 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 3.9/10; 76% of recent commits are signed; last pushed 2026-03-11. 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-07-29
Rank Moved
Rank dropped 10 spots (#375 → #385)
2026-07-15
Rank Moved
Rank dropped 24 spots (#341 → #365)
2026-07-14
Rank Moved
Rank dropped 19 spots (#322 → #341)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.9/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.
Refresh maintenance signals The repo was last pushed 148 days ago. Fresh activity helps separate stable projects from stale ones.
34.7
Activity sub-score · out of 100
#80

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-08-06 02:30 UTC · Repo last pushed 148 days ago

Rank Trend

2026-07-05 2026-08-06

Activity & Reach

Stars
2.4k
Forks
127
Last Push
2026-03-11
148 days ago
Commits (4 wk)
0
Downloads (7d)
HN mentions (30d)
Open Issues
40
Rank Change
=
was #385

Analysis

HVTrust Dimensions vs Agent Frameworks

37.8 / 100 · 100.0% confidence

Magentic Agent Frameworks average (103 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.7 / 25
in line with avg 9.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
11.8 / 17
in line with avg 12.0
Maintenance60% last-push freshness · 40% commit activity
2.1 / 20
12.5 below avg 14.6
AdoptionLog-scaled stars · package downloads
8.1 / 20
3.8 below avg 11.9

Activity Inputs

34.7 / 100
StarsRepository reach
20.3 / 30
FreshnessLast push recency
4.4 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
9.8 / 20

Supply Chain Trust

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

Is Magentic safe?

Public trust evidence for Magentic 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 Magentic publish package provenance?
No published build provenance is currently detected for Magentic. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Magentic have an OpenSSF Scorecard?
Magentic has an OpenSSF Scorecard score of 3.9/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 Magentic actively maintained?
Slowing down. Last push was 148 days ago — keep an eye on whether activity resumes.
What license does Magentic use?
Magentic ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Magentic's commits signed?
76% of the last 100 commits to Magentic 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
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
4 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • code
  • search
  • shell
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 Magentic?

For maintainers

HVTrust scores Magentic 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 6Listed 1HVTrust 1Scorecard 1
2026-07-29
Rank Moved
Rank dropped 10 spots (#375 → #385)
2026-07-15
Rank Moved
Rank dropped 24 spots (#341 → #365)
2026-07-14
Rank Moved
Rank dropped 19 spots (#322 → #341)
2026-07-13
Rank Moved
Rank dropped 37 spots (#285 → #322)
2026-06-24
Rank Moved
Rank dropped 31 spots (#232 → #263)
2026-06-23
Scorecard Added
OSSF Scorecard: 3.9/10
2026-06-23
Rank Moved
Rank rose 63 spots (#295 → #232)
2026-06-23
HVTrust Changed
HVTrust up 26.3pts (18.2 → 44.5)
2026-06-21
Newly Listed
First tracked at rank #294

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 37.8 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/magentic.svg)](https://hvtracker.net/agents/magentic)
HTML:
<a href="https://hvtracker.net/agents/magentic"><img src="https://hvtracker.net/badge/magentic.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.2 · Raw JSON