updated 2026-10-09 08:15 UTC

OpenSSA

Repository Website

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

Agent Frameworks Python Needs review NOASSERTION

Is OpenSSA safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.7 / 10
Provenance None
Signed commits 42%
Last push 421d ago
Advisories None known
Compare OpenSSA

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →
Suggest a correction

In detail: OpenSSA scores 30.9/100 (Grade D), ranked #1295 of 1371 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; no published advisory affects its latest release (openssa); last pushed 2025-08-14. Every point is earned from checkable signals — never paid placement. How scoring works →

How OpenSSA 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.

Already done? Suggest a correctionAdd the trust badge
Active listing, but review is needed
  • [4.2.1] no meaningful activity in 12 months (last push 2025-08-14)

Chain of custody

Scanners check what the code says. This traces who ships OpenSSA and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/aitomatic/openssa, NOASSERTION, last pushed 2025-08-14. 42% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.7/10 (scanned Sep 22, 2026, refresh pending). The checks that decide who can get a change released:

    • Code Review10
    • Branch Protection6
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    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

  3. Published packages Linked, not attested

    • PyPI openssa Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: openssa 0.24.12.12. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of OpenSSA.

Evidence behind this score

Coverage A: 4 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions

Verify this score yourself

Every build re-issues OpenSSA’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.

Signed credential (JSON) How to verify

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 OpenSSA compares in Agent Frameworks

  1. #111 Magentic 35.2 +4.3
  2. #112 Youtu-Agent 32.4 +1.5
  3. #113 OpenSSA 30.9 this agent
  4. #114 xpander.ai 30.9 ±0
  5. #115 AutoAgent 30.4 −0.5

Bars show each HVTrust score; the tick marks OpenSSA’s 30.9.

Where the 30.9 comes from

HVTrust dimensions vs the Agent Frameworks average

30.9 / 100 · 100.0% confidence

OpenSSA Agent Frameworks average (129 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.7 / 25
2.8 below avg 9.5
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 12.0
Maintenance60% last-push freshness · 40% commit activity
0 / 20
13.6 below avg 13.6
AdoptionLog-scaled stars · package downloads
7.8 / 20
3.0 below avg 10.8

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-23
Rank Moved
Rank dropped 605 spots (#672 → #1277)
2026-09-22
Rank Moved
Rank dropped 256 spots (#416 → #672)
2026-09-21
Rank Moved
Rank rose 865 spots (#1281 → #416)
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 421 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
#113
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 →

Signals refreshed 2026-10-09 08:15 UTC · Repo last pushed 421 days ago — may be stale

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
351
Forks
61
Last Push
2025-08-14
421 days ago
Commits (4 wk)
0
Downloads (7d)
17
pypi
HN mentions (30d)
409
Open Issues
10
Rank Change
▼2
was #1293

Analysis

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

Common questions about OpenSSA

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 421 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.
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
Rank 25Warning Issued 1HVTrust 1
2026-09-23
Rank Moved
Rank dropped 605 spots (#672 → #1277)
2026-09-22
Rank Moved
Rank dropped 256 spots (#416 → #672)
2026-09-21
Rank Moved
Rank rose 865 spots (#1281 → #416)
2026-09-10
Rank Moved
Rank dropped 13 spots (#1273 → #1286)
2026-09-08
Rank Moved
Rank dropped 12 spots (#1254 → #1266)
2026-09-07
Rank Moved
Rank dropped 11 spots (#1243 → #1254)
2026-09-06
Rank Moved
Rank dropped 17 spots (#1226 → #1243)
2026-09-05
Rank Moved
Rank dropped 22 spots (#1204 → #1226)
2026-09-03
Rank Moved
Rank dropped 41 spots (#1157 → #1198)
2026-09-02
Rank Moved
Rank dropped 39 spots (#1118 → #1157)
2026-09-01
Rank Moved
Rank dropped 41 spots (#1077 → #1118)
2026-08-31
Rank Moved
Rank dropped 33 spots (#1044 → #1077)
2026-08-30
Rank Moved
Rank dropped 52 spots (#992 → #1044)
2026-08-29
Rank Moved
Rank dropped 56 spots (#936 → #992)
2026-08-28
Rank Moved
Rank dropped 34 spots (#902 → #936)
2026-08-27
Rank Moved
Rank dropped 31 spots (#871 → #902)
2026-08-26
Rank Moved
Rank dropped 109 spots (#762 → #871)
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)
GitHub → Website → PyPI: openssa

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 30.9 Grade D
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.4 · Raw JSON