Is smolagents safe?
smolagents scores 65.1/100 (Grade B), ranked #121 of 328 tracked open-source AI agent projects, on evidence coverage A (4 of 5 independent signal types).
The public evidence: no package-provenance attestation found;
OSSF Scorecard rates its supply-chain practices 5.8/10;
100% of recent commits are signed;
last pushed 2026-07-10. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Promising trust profile, but some evidence still deserves review.
65.1/100 · Grade B
Strongest Signal
Adoption
17.6/20
Weakest Signal
Safety / Integrity
12.2/25
What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-07-10
Grade Changed
Trust grade C → B
2026-07-10
Rank Moved
Rank rose 12 spots (#132 → #120)
2026-07-10
Activity Score Changed
Activity score up 7pts (69 → 76)
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 5.8/10. Tighten the weakest checks to improve public safety evidence.
Publish provenanceAdd package provenance or release attestations so users can verify where shipped artifacts came from.
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 A is separate — it grades how many independent signal types back the score (4 of 5), so a high score on thin evidence stays visible. Full methodology →
Signals refreshed2026-07-11 04:00 UTC·Repo last pushed yesterday
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
28.3k
Forks
2.8k
Last Push
2026-07-10
yesterday
Commits (4 wk)
4?
Downloads (7d)
156,307
pypi
HN mentions (30d)
0
Open Issues
274
Rank Change
▼1
was #120
Analysis
HVTrust Dimensions
65.1 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
12.2 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
13.4 / 17
MaintenanceFreshness and commits
13.3 / 20
AdoptionStars and downloads
17.6 / 20
Activity Inputs
76.4 / 100
StarsRepository reach
26.7 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
8.7 / 25
CommunityFork signal
16.0 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
5.8 / 10
OpenSSF Scorecard · scanned Jul 10, 2026
Signed Commits
100%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection6
CI-Tests8
CII-Best-Practices0
Code-Review2
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License10
Maintained10
Packaging-1
Pinned-Dependencies6
SAST0
Security-Policy10
Signed-Releases-1
Token-Permissions0
Vulnerabilities0
Is smolagents safe?
smolagents 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 smolagents publish package provenance?
No published build provenance is currently detected for smolagents. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does smolagents have an OpenSSF Scorecard?
smolagents has an OpenSSF Scorecard score of 5.8/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 smolagents actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does smolagents use?
smolagents ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are smolagents's commits signed?
100% of the last 100 commits to smolagents 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 → Compare this surface across every listed agent in the capability matrix →
MCP Server Support
medium confidence
Implemented
smolagents appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
Credential signal:
API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
browser
code
search
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
Detailed evidence is not shown in the public view.
MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live
How this surface has changed
Detected changes to smolagents's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Detected MCP server support changed: none → implemented
Maintain smolagents?
HVTrust scores smolagents 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.
