ASM

The universal skill manager for AI coding agents.

Needs review TypeScript Grade B Listed MIT
65.0/100
Rank #443 of 1328
Compare ASM

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-09-09 · 2d ago
Recent change
Rank +4

Is ASM safe? ASM scores 65.0/100 (Grade B), ranked #443 of 1328 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 6.8/10; 88% of recent commits are signed; last pushed 2026-09-09. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Needs review

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-10
Rank Moved
Rank dropped 10 spots (#435 → #445)
2026-09-08
Rank Moved
Rank dropped 13 spots (#421 → #434)
2026-09-07
Rank Moved
Rank dropped 23 spots (#398 → #421)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.8/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.
76.6
Activity sub-score · out of 100
#2

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

Signals refreshed 2026-09-11 00:32 UTC · Repo last pushed 2 days ago

Rank Trend

2026-08-11 2026-09-11

Activity & Reach

Stars
916
Forks
83
Last Push
2026-09-09
2 days ago
Commits (4 wk)
110
Downloads (7d)
HN mentions (30d)
Open Issues
14
Rank Change
▲2
was #445

Analysis

HVTrust Dimensions vs Needs review

65.0 / 100 · 100.0% confidence

ASM Needs review average (11 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.9 / 25
4.8 above avg 8.1
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
in line with avg 10.8
Transparency50% declared license · 50% OSSF Scorecard
14.3 / 17
1.9 above avg 12.4
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
4.8 above avg 15.1
AdoptionLog-scaled stars · package downloads
7.1 / 20
2.0 below avg 9.1

Activity Inputs

76.6 / 100
StarsRepository reach
17.8 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
8.9 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
6.8 / 10
OpenSSF Scorecard · scanned Sep 4, 2026
Signed Commits
88%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 3
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 9
SAST 0
Security-Policy 10
Signed-Releases -1
Token-Permissions 10
Vulnerabilities 10

Is ASM safe?

ASM 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 ASM publish package provenance?
No published build provenance is currently detected for ASM. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does ASM have an OpenSSF Scorecard?
ASM has an OpenSSF Scorecard score of 6.8/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 ASM actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does ASM use?
ASM ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are ASM's commits signed?
88% of the last 100 commits to ASM 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.

Compare ASM head-to-head

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
None detected
No clear third-party provider dependency 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
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 ASM?

For maintainers

HVTrust scores ASM 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 23Grade 2HVTrust 1Scorecard 1
2026-09-10
Rank Moved
Rank dropped 10 spots (#435 → #445)
2026-09-08
Rank Moved
Rank dropped 13 spots (#421 → #434)
2026-09-07
Rank Moved
Rank dropped 23 spots (#398 → #421)
2026-09-05
Rank Moved
Rank dropped 66 spots (#325 → #391)
2026-09-04
Rank Moved
Rank dropped 10 spots (#315 → #325)
2026-09-03
Grade Changed
Trust grade C → B
2026-09-03
Rank Moved
Rank rose 21 spots (#336 → #315)
2026-08-31
Rank Moved
Rank dropped 30 spots (#296 → #326)
2026-08-30
Rank Moved
Rank rose 12 spots (#308 → #296)
2026-08-29
Rank Moved
Rank dropped 16 spots (#292 → #308)
2026-08-26
Rank Moved
Rank dropped 22 spots (#267 → #289)
2026-08-24
Rank Moved
Rank dropped 18 spots (#257 → #275)
2026-08-22
Rank Moved
Rank rose 12 spots (#269 → #257)
2026-08-21
Rank Moved
Rank rose 29 spots (#298 → #269)
2026-08-19
Rank Moved
Rank rose 14 spots (#317 → #303)
2026-08-17
Rank Moved
Rank rose 27 spots (#348 → #321)
2026-08-13
Rank Moved
Rank dropped 18 spots (#321 → #339)
2026-08-12
Rank Moved
Rank rose 15 spots (#336 → #321)
2026-08-08
Rank Moved
Rank dropped 81 spots (#243 → #324)
2026-07-14
Rank Moved
Rank dropped 13 spots (#191 → #204)
2026-07-13
Rank Moved
Rank dropped 29 spots (#162 → #191)
2026-06-29
Rank Moved
Rank rose 13 spots (#190 → #177)
2026-06-24
Rank Moved
Rank dropped 20 spots (#165 → #185)
2026-06-18
Scorecard Added
OSSF Scorecard: 6.1/10
2026-06-18
Grade Changed
Trust grade D → C
2026-06-18
Rank Moved
Rank rose 81 spots (#225 → #144)
2026-06-18
HVTrust Changed
HVTrust up 36.1pts (23.2 → 59.3)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 65.0 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/asm.svg)](https://hvtracker.net/agents/asm)
HTML:
<a href="https://hvtracker.net/agents/asm"><img src="https://hvtracker.net/badge/asm.svg" alt="HVTrust"></a>

Other agents in Needs review

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