sre
Website
The SmythOS Runtime Environment (SRE) is an open-source, cloud-native runtime for agentic AI. Secure, modular, and production-ready, it lets developers build, run, and manage intelligent agents across local, cloud, and edge environments.
Is sre safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare sre
How does it stack up against its Agent Frameworks neighbours?
Pick any agent to compare →In detail: sre scores 36.7/100 (Grade D), ranked #1263 of 1374 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.3/10; 36% of recent commits are signed; last pushed 2026-04-03. Every point is earned from checkable signals — never paid placement. How scoring works →
How sre could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Raise the OSSF Scorecard from 4.3 to 9.0lowest checks: CI-Tests 0, CII-Best-Practices 0, Dependency-Update-Tool 0 +9.8 → 46.5 D · #102 of 130
- Sign every commit36% signed today +3.2 → 39.9 D · #110 of 130
Chain of custody
Scanners check what the code says. This traces who ships sre and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/SmythOS/sre, MIT, last pushed 2026-04-03. 36% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 4.3/10 (scanned Oct 31, 2026). The checks that decide who can get a change released:
- Code Review6
- Branch Protection3
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions9
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 3CI-Tests 0CII-Best-Practices 0Code-Review 6Contributors 6Dangerous-Workflow 10Dependency-Update-Tool 0Fuzzing 0License 10Maintained 0Packaging -1Pinned-Dependencies 0SAST 0Security-Policy 10Signed-Releases -1Token-Permissions 9Vulnerabilities 0 -
Published packages None
No registry package. sre is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
- 2026-08-26 OSSF Scorecard: 4.3/10
Evidence behind this score
Coverage C: 2 of 5 independent evidence types found.
- GitHub repository data
- Package downloads (missing)
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues sre’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How sre compares in Agent Frameworks
- #110 omniclaw 39.4 +2.7
- #111 Upsonic 37.9 +1.2
- #112 sre 36.7 this agent
- #113 AgentLite 36.6 −0.1
- #114 harmonist 36.5 −0.2
Bars show each HVTrust score; the tick marks sre’s 36.7.
Where the 36.7 comes from
HVTrust dimensions vs the Agent Frameworks average
36.7 / 100 · 100.0% confidencesre Agent Frameworks average (130 agents)
Quick Trust Read
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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
29.4 / 100Common questions about sre
Does sre publish package provenance?
Does sre have an OpenSSF Scorecard?
Is sre actively maintained?
What license does sre use?
Are sre's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to sre'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.
Maintain sre?
For maintainers
HVTrust scores sre 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
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/sre)
<a href="https://hvtracker.net/agents/sre"><img src="https://hvtracker.net/badge/sre.svg" alt="HVTrust"></a>
Other agents in Agent Frameworks
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON