Is OpenSSA safe to use?

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

What is the trust score for OpenSSA?

OpenSSA scores 31.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 348 GitHub stars and is categorized under Agent Frameworks.

OpenSSA

aitomatic/openssa

OpenSSA: Small Specialist Agents based on Domain-Aware Neurosymbolic Agent (DANA) architecture for industrial problem-so

Agent Frameworks Python Grade D Needs review NOASSERTION

31.3/100

Rank #757 of 1308

Compare OpenSSA

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

Needs review

Evidence coverage

Grade A · 4/5 signals

Last push

2025-08-14 · 376d ago

Recent change

No recent signal change

Is OpenSSA safe? OpenSSA scores 31.3/100 (Grade D), ranked #757 of 1308 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 3.7/10; 42% of recent commits are signed; last pushed 2025-08-14. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

#83 Lingxi — 32.5 (D) → #84 OpenManus — 31.6 (D) → #86 AutoAgent — 30.4 (D) → #87 BabyAGI — 30.2 (D) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-16

Rank Moved

Rank dropped 13 spots (#742 → #755)

2026-08-15

Rank Moved

Rank dropped 152 spots (#590 → #742)

2026-08-15

HVTrust Changed

HVTrust down 10.0pts (41.7 → 31.7)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.7/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.

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

Review Flags

[4.2.1] no meaningful activity in 12 months (last push 2025-08-14)

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

23.6

Activity sub-score · out of 100

#85

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 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 →

Rank Trend

2026-08-11 2026-08-25

Activity & Reach

Stars

348

Forks

Last Push

2025-08-14

376 days ago

Commits (4 wk)

Downloads (7d)

pypi

HN mentions (30d)

676

Open Issues

Rank Change

▲6

was #763

Analysis

HVTrust Dimensions vs Agent Frameworks

31.3 / 100 · 100.0% confidence

OpenSSA Agent Frameworks average (119 agents)

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

6.7 / 25

1.4 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

11.6 / 17

in line with avg 11.5

Maintenance60% last-push freshness · 40% commit activity

0 / 20

14.2 below avg 14.2

AdoptionLog-scaled stars · package downloads

8.2 / 20

3.1 below avg 11.3

Activity Inputs

23.6 / 100

StarsRepository reach

15.3 / 30

FreshnessLast push recency

0.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

8.3 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.7 / 10

OpenSSF Scorecard · scanned Aug 25, 2026

Signed Commits

42%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 6

CI-Tests 0

CII-Best-Practices 0

Code-Review 10

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 9

Maintained 0

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Is OpenSSA safe?

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

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

Does OpenSSA have an OpenSSF Scorecard?

OpenSSA has an OpenSSF Scorecard score of 3.7/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 OpenSSA actively maintained?

Stale. The repository has not been pushed to in 376 days. Consider whether the project is still being maintained.

What license does OpenSSA use?

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

Are OpenSSA's commits signed?

42% of the last 100 commits to OpenSSA 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

medium confidence

1 detected

Public provider/service dependencies detected.

OpenAI

Credential signal: No explicit API-key/config marker detected.

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

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain OpenSSA?

For maintainers

HVTrust scores OpenSSA 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 13 spots (#742 → #755)

2026-08-15

Rank Moved

Rank dropped 152 spots (#590 → #742)

2026-08-15

HVTrust Changed

HVTrust down 10.0pts (41.7 → 31.7)

2026-08-14

Warning Issued

Warning: eligibility issues detected

2026-08-10

Rank Moved

Rank dropped 22 spots (#560 → #582)

2026-08-08

Rank Moved

Rank dropped 180 spots (#380 → #560)

2026-07-29

Rank Moved

Rank dropped 10 spots (#360 → #370)

2026-07-15

Rank Moved

Rank dropped 23 spots (#329 → #352)

2026-07-14

Rank Moved

Rank dropped 23 spots (#306 → #329)

2026-07-13

Rank Moved

Rank dropped 30 spots (#276 → #306)

2026-06-24

Rank Moved

Rank dropped 36 spots (#259 → #295)

2026-06-23

Rank Moved

Rank dropped 22 spots (#237 → #259)

2026-06-21

Rank Moved

Rank dropped 13 spots (#218 → #231)

2026-06-10

Rank Moved

Rank dropped 10 spots (#187 → #197)

2026-06-08

Rank Moved

Rank dropped 10 spots (#181 → #191)

2026-06-02

Rank Moved

Rank dropped 15 spots (#164 → #179)

2026-06-01

Rank Moved

Rank dropped 19 spots (#145 → #164)

2026-05-29

HVTrust Changed

HVTrust up 10.0pts (28.0 → 38.0)

GitHub → PyPI: openssa

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Agent Frameworks

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