Atomic Agents

Building AI agents, atomically

Agent Frameworks Python Listed MIT

Is Atomic Agents safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.9 / 10
Provenance None
Signed commits 38%
Last push 5d ago
Advisories None known
Compare Atomic Agents
Suggest a correction

In detail: Atomic Agents scores 64.8/100 (Grade C), ranked #500 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 4.9/10; 38% of recent commits are signed; no published advisory affects its latest release (atomic-agents); last pushed 2026-10-04. Every point is earned from checkable signals — never paid placement. How scoring works →

How Atomic Agents 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.

Chain of custody

Scanners check what the code says. This traces who ships Atomic Agents 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/Eigenwise/atomic-agents, MIT, last pushed 2026-10-04. 38% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

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

    • Code Review3
    • Branch Protection5
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 5
    CI-Tests 8
    CII-Best-Practices 0
    Code-Review 3
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 10
    Vulnerabilities 0
  3. Published packages Linked, not attested

    • PyPI atomic-agents 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: atomic-agents 2.10.3. No published advisory affects it (OSV, checked 2026-10-09).

Changes to this chain

  • 2026-10-02 Provenance drift warning cleared (now: unknown)

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 Atomic Agents’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 Atomic Agents compares in Agent Frameworks

  1. #40 Mastra 65.6 +0.8
  2. #41 TrueForge 65.5 +0.7
  3. #42 Atomic Agents 64.8 this agent
  4. #43 smolagents 64.7 −0.1
  5. #44 neuro-san-studio 64.1 −0.7

Bars show each HVTrust score; the tick marks Atomic Agents’s 64.8.

Where the 64.8 comes from

HVTrust dimensions vs the Agent Frameworks average

64.8 / 100 · 100.0% confidence

Atomic Agents Agent Frameworks average (129 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.0 / 25
1.5 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
12.7 / 17
0.7 above avg 12.0
Maintenance60% last-push freshness · 40% commit activity
16.1 / 20
2.5 above avg 13.6
AdoptionLog-scaled stars · package downloads
13.8 / 20
3.0 above avg 10.8

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-09
Grade Changed
Trust grade B → C
2026-10-08
Grade Changed
Trust grade C → B
2026-10-07
Grade Changed
Trust grade B → C
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.9/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.
73.9
Activity sub-score · out of 100
#42

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C 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 5 days ago

Rank Trend

2026-09-29 2026-10-09

Activity & Reach

Stars
6.3k
Forks
553
Last Push
2026-10-04
5 days ago
Commits (4 wk)
12
Downloads (7d)
3,542
pypi
HN mentions (30d)
0
Open Issues
3
Rank Change
▼9
was #491

Analysis

Activity Inputs

73.9 / 100
StarsRepository reach
22.8 / 30
FreshnessLast push recency
24.3 / 25
ActivityRecent commits
13.9 / 25
CommunityFork signal
12.8 / 20

Common questions about Atomic Agents

Atomic Agents 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 Atomic Agents publish package provenance?
No published build provenance is currently detected for Atomic Agents. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Atomic Agents have an OpenSSF Scorecard?
Atomic Agents has an OpenSSF Scorecard score of 4.9/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 Atomic Agents actively maintained?
Actively maintained. The repository was pushed to within the last 5 day(s).
What license does Atomic Agents use?
Atomic Agents ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Atomic Agents's commits signed?
38% of the last 100 commits to Atomic Agents 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
high confidence
Implemented
Atomic Agents appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
5 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • code
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
How this surface has changed

Detected changes to Atomic Agents'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.

2026-10-02
Drift Warning Cleared
Provenance drift warning cleared (now: unknown)
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: marketplace → declared
2026-07-19
Tool Surface Changed
Detected tool/plugin surface changed: declared → marketplace
2026-07-19
Mcp Status Changed
Detected MCP server support changed: declared → implemented
2026-07-17
Provider Added
Runtime surface grew — new detected provider dependencies: Google Gemini, Groq, Multi-provider (LiteLLM)

Maintain Atomic Agents?

For maintainers

HVTrust scores Atomic Agents 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
Rank 37Grade 6HVTrust 3Surface 2Score 2Surface 1MCP 1Drift 1
2026-10-09
Grade Changed
Trust grade B → C
2026-10-08
Grade Changed
Trust grade C → B
2026-10-07
Grade Changed
Trust grade B → C
2026-10-07
Rank Moved
Rank dropped 15 spots (#482 → #497)
2026-10-04
Grade Changed
Trust grade C → B
2026-10-04
Rank Moved
Rank rose 21 spots (#506 → #485)
2026-10-03
Rank Moved
Rank rose 128 spots (#634 → #506)
2026-10-03
HVTrust Changed
HVTrust up 4.1pts (60.2 → 64.3)
2026-10-02
Drift Warning Cleared
Provenance drift warning cleared (now: unknown)
2026-10-02
Rank Moved
Rank rose 157 spots (#791 → #634)
2026-10-02
HVTrust Changed
HVTrust up 5.1pts (55.1 → 60.2)
2026-10-01
Rank Moved
Rank dropped 10 spots (#781 → #791)
2026-09-27
Grade Changed
Trust grade D → C
2026-09-27
Rank Moved
Rank rose 192 spots (#960 → #768)
2026-09-27
HVTrust Changed
HVTrust up 6.4pts (49.1 → 55.5)
2026-09-27
Activity Score Changed
Activity score up 18pts (56 → 74)
2026-09-25
Rank Moved
Rank dropped 11 spots (#942 → #953)
2026-09-23
Grade Changed
Trust grade C → D
2026-09-23
Rank Moved
Rank dropped 620 spots (#319 → #939)
2026-09-23
Activity Score Changed
Activity score down 9pts (65 → 56)
2026-09-21
Rank Moved
Rank rose 547 spots (#858 → #311)
2026-09-19
Rank Moved
Rank dropped 41 spots (#808 → #849)
2026-09-18
Rank Moved
Rank dropped 10 spots (#798 → #808)
2026-09-11
Rank Moved
Rank dropped 13 spots (#767 → #780)
2026-09-10
Rank Moved
Rank dropped 24 spots (#743 → #767)
2026-09-09
Rank Moved
Rank dropped 15 spots (#728 → #743)
2026-09-08
Rank Moved
Rank dropped 11 spots (#717 → #728)
2026-09-07
Rank Moved
Rank dropped 39 spots (#678 → #717)
2026-09-06
Rank Moved
Rank dropped 14 spots (#664 → #678)
2026-09-05
Rank Moved
Rank dropped 79 spots (#585 → #664)
2026-09-04
Rank Moved
Rank dropped 17 spots (#568 → #585)
2026-09-03
Rank Moved
Rank dropped 41 spots (#527 → #568)
2026-09-02
Rank Moved
Rank dropped 19 spots (#508 → #527)
2026-09-01
Rank Moved
Rank dropped 15 spots (#493 → #508)
2026-08-31
Rank Moved
Rank dropped 30 spots (#463 → #493)
2026-08-29
Rank Moved
Rank dropped 14 spots (#453 → #467)
2026-08-27
Rank Moved
Rank dropped 17 spots (#428 → #445)
2026-08-26
Rank Moved
Rank dropped 40 spots (#388 → #428)
2026-08-22
Rank Moved
Rank rose 18 spots (#396 → #378)
2026-08-20
Rank Moved
Rank rose 14 spots (#402 → #388)
2026-08-19
Rank Moved
Rank dropped 14 spots (#388 → #402)
2026-08-13
Rank Moved
Rank dropped 16 spots (#368 → #384)
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: marketplace → declared
2026-08-12
Rank Moved
Rank rose 23 spots (#391 → #368)
2026-08-10
Rank Moved
Rank dropped 19 spots (#381 → #400)
2026-08-08
Rank Moved
Rank dropped 90 spots (#270 → #360)
2026-07-19
Tool Surface Changed
Detected tool/plugin surface changed: declared → marketplace
2026-07-19
Mcp Status Changed
Detected MCP server support changed: declared → implemented
2026-07-19
Rank Moved
Rank rose 10 spots (#263 → #253)
2026-07-17
Provider Added
Runtime surface grew — new detected provider dependencies: Google Gemini, Groq, Multi-provider (LiteLLM)
2026-07-17
Rank Moved
Rank dropped 11 spots (#255 → #266)
2026-07-15
Rank Moved
Rank dropped 28 spots (#227 → #255)
2026-07-13
Rank Moved
Rank dropped 15 spots (#204 → #219)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 64.8 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/atomic-agents.svg)](https://hvtracker.net/agents/atomic-agents)
HTML:
<a href="https://hvtracker.net/agents/atomic-agents"><img src="https://hvtracker.net/badge/atomic-agents.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