Is Acontext safe to use?

Acontext has an HVTrust score of 43.3/100 (Grade D), ranked #298 of 351 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Acontext?

Acontext scores 43.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 3.7k GitHub stars and is categorized under Agent Skills.

Acontext

memodb-io/Acontext

Agent Skills as a Memory Layer

Agent Skills JavaScript Listed Apache-2.0

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

OSSF Scorecard 4.0 / 10

Provenance None

Signed commits 59%

Last push 74d ago

Compare Acontext

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Acontext scores 43.3/100 (Grade D), ranked #298 of 351 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.0/10; 59% of recent commits are signed; last pushed 2026-07-14. Every point is earned from checkable signals — never paid placement. How scoring works →

How Acontext compares in Agent Skills

#296 Claude Code Settings 43.8 +0.5
#297 Vuejs Skills 43.4 +0.1
#298 Acontext 43.3 this agent
#299 Claude For Financial Services Cn 43.1 −0.2
#300 Super Agent Party 42.9 −0.4

Bars show each HVTrust score; the tick marks Acontext’s 43.3.

Where the 43.3 comes from

HVTrust dimensions vs the Agent Skills average

43.3 / 100 · 100.0% confidence

Acontext Agent Skills average (351 agents)

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

8.0 / 25

in line with avg 8.1

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.6 below avg 11.4

Transparency50% declared license · 50% OSSF Scorecard

11.9 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

7.1 / 20

7.1 below avg 14.2

AdoptionLog-scaled stars · package downloads

8.6 / 20

in line with avg 9.0

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-25

Rank Moved

Rank dropped 23 spots (#274 → #297)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI, Postgres, Supabase

Maintainer Checklist

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

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

Compare with another agent Get email alerts for Acontext View Agent Skills Report missing data

48.0

Activity sub-score · out of 100

#298

In Agent Skills

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

2026-08-11 2026-09-26

Activity & Reach

Stars

3.7k

Forks

334

Last Push

2026-07-14

74 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #297

Analysis

Activity Inputs

48.0 / 100

StarsRepository reach

21.4 / 30

FreshnessLast push recency

14.7 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

11.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.0 / 10

OpenSSF Scorecard · scanned Sep 26, 2026

Signed Commits

59%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 10

CII-Best-Practices 0

Code-Review 2

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 6

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Common questions about Acontext

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

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

Does Acontext have an OpenSSF Scorecard?

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

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

What license does Acontext use?

Acontext ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Acontext's commits signed?

59% of the last 100 commits to Acontext 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

4 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

database

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

How this surface has changed

Detected changes to Acontext'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-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI, Postgres, Supabase

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

Maintain Acontext?

For maintainers

HVTrust scores Acontext 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-09-25

Rank Moved

Rank dropped 23 spots (#274 → #297)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, OpenAI, Postgres, Supabase

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → declared

2026-09-23

Rank Moved

Rank dropped 73 spots (#200 → #273)

2026-09-23

HVTrust Changed

HVTrust up 8.4pts (35.1 → 43.5)

2026-09-22

Newly Listed

First tracked at rank #200

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-10

Rank Moved

Rank dropped 10 spots (#238 → #248)

2026-09-05

Rank Moved

Rank dropped 11 spots (#202 → #213)

2026-09-01

Rank Moved

Rank dropped 16 spots (#165 → #181)

2026-08-31

Rank Moved

Rank dropped 18 spots (#147 → #165)

2026-08-30

Rank Moved

Rank dropped 28 spots (#119 → #147)

2026-08-29

Rank Moved

Rank dropped 27 spots (#92 → #119)

2026-08-28

Rank Moved

Rank dropped 21 spots (#71 → #92)

2026-08-27

Rank Moved

Rank dropped 20 spots (#51 → #71)

2026-08-26

Scorecard Added

OSSF Scorecard: 4.0/10

2026-08-26

Rank Moved

Rank rose 93 spots (#144 → #51)

2026-08-26

HVTrust Changed

HVTrust up 28.4pts (16.9 → 45.3)

2026-08-16

Rank Moved

Rank dropped 11 spots (#133 → #144)

2026-08-11

Newly Listed

First tracked at rank #133

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Agent Skills

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