sre has an HVTrust score of 14.7/100 (Grade D), ranked #1272 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for sre?

sre scores 14.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.3k GitHub stars and is categorized under Agent Frameworks.

sre

SmythOS/sre

The SmythOS Runtime Environment (SRE) is an open-source, cloud-native runtime for agentic AI. Secure, modular, and produ

Agent Frameworks TypeScript Grade D Listed MIT

14.7/100

Rank #1272 of 1308

Compare sre

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →

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

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade D · 1/5 signals

Last push

2026-04-03 · 138d ago

Recent change

Rank

Is sre safe? sre scores 14.7/100 (Grade D), ranked #1272 of 1308 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 36% of recent commits are signed; last pushed 2026-04-03. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

#112 harmonist — 17.4 (D) → #113 AIlice — 15.7 (D) → #115 cashclaw — 14.1 (D) → #116 daydreams — 13.4 (D) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-16

Rank Moved

Rank dropped 27 spots (#1245 → #1272)

2026-08-10

Rank Moved

Rank dropped 77 spots (#1162 → #1239)

2026-08-08

Rank Moved

Rank dropped 653 spots (#509 → #1162)

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

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.

Refresh maintenance signals The repo was last pushed 138 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for sre View Agent Frameworks Report missing data

35.2

Activity sub-score · out of 100

#114

In Agent Frameworks

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

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars

1.3k

Forks

201

Last Push

2026-04-03

138 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #1271

Analysis

HVTrust Dimensions vs Agent Frameworks

14.7 / 100 · 50.0% confidence

sre Agent Frameworks average (119 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

1.8 / 25

6.3 below avg 8.1

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

3.0 below avg 11.5

Maintenance60% last-push freshness · 40% commit activity

2.8 / 20

11.6 below avg 14.4

AdoptionLog-scaled stars · package downloads

7.5 / 20

3.8 below avg 11.3

Activity Inputs

35.2 / 100

StarsRepository reach

18.7 / 30

FreshnessLast push recency

5.8 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

10.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

36%

of last 100 commits verified

Is sre safe?

Public trust evidence for sre 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 sre publish package provenance?

No published build provenance is currently detected for sre. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does sre have an OpenSSF Scorecard?

No OpenSSF Scorecard data is currently published for sre. 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 sre actively maintained?

Slowing down. Last push was 138 days ago — keep an eye on whether activity resumes.

What license does sre use?

sre ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are sre's commits signed?

36% of the last 100 commits to sre 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

1 detected

Public provider/service dependencies detected.

Pinecone

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool 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 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-16

Rank Moved

Rank dropped 27 spots (#1245 → #1272)

2026-08-10

Rank Moved

Rank dropped 77 spots (#1162 → #1239)

2026-08-08

Rank Moved

Rank dropped 653 spots (#509 → #1162)

2026-08-06

Newly Listed

First tracked at rank #514

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/sre.svg)](https://hvtracker.net/agents/sre)
            
HTML:
            <a href="https://hvtracker.net/agents/sre"><img src="https://hvtracker.net/badge/sre.svg" alt="HVTrust"></a>

Other agents in Agent Frameworks

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