Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-22 07:49 UTC

itlackey / akm

Agent Knowledge Manager (akm). A CLI tool to manage AI agent knowledge, memories, skills, and more.

TypeScriptMPL-2.0★ 66 stars⑂ 4 forkssince Mar 2026View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

itlackey/akm holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Vitality (87/100) and lowest on Security (46/100). It was last updated today. A single contributor accounts for most of its recent work.

80
overall / 100
Excellent

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

80
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 68 is calibrated to 80 on the published index scale (record calibration 2026-08-02).

Ownership

IT LackeyPersonal account
41 followers84 public repossince Jan 2014Washington University in St. Louis

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

87Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
20.8/36Commit cadence — 30/52 weeks with commits
18/18Commit volume — 5,351 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 30 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year5,351
human_commit_share1
days_since_last_push0
active_weeks_last_year30
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~1 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagv0.10.261010-beta
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases1

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

58Moderate · 17% of overall
How it's scored
29.4/60Stars — 66 stars
4/25Forks — 4 forks
0/15Watchers — 1 watchers
Inputs used
forks4
stars66
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MPL-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes
How it's scored
56.8/80Monthly downloads — 18,190 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesakm-cli
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads18,190
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

63Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
6.3/22.5Commit distribution — top contributor authored 72% of commits
6.8/13.5Contributor breadth — 5 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled5
top_contributor_share0.721
How it's scored
40.7/42Issue resolution — 97% of issues closed
29/30PR acceptance — 567/587 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 1/18 approved changesets -- score normalized to 0
Inputs used
merged_prs567
open_issues19
closed_issues620
prs_merged_7d23
prs_decided_7d23
prs_merged_30d59
prs_decided_30d60
issue_closed_ratio0.97
closed_unmerged_prs20
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
11.7/25Owner reach — 41 followers of itlackey
25/25Track record — 84 public repos, account ~12 yr old
Inputs used
followers41
owner_typeUser
is_verified—
owner_loginitlackey
public_repos84
account_age_days4,662
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 8 days ago
20/20Version history — 213 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesakm-cli
ecosystemsnpm
any_deprecatedno
min_days_since_publish8

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
16/16Linter config — biome.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
12/20OpenSSF Scorecard: CI-Tests — 9 out of 15 merged PRs checked by a CI test -- score normalized to 6
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

85Excellent
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 12 topics
10/10Wiki
Inputs used
topicsagent-tools, ai-agents, ai-coding-assistant, ai-skills, akm, claude-code, cli, developer-tools, mcp, opencode, package-manager, agent-kit-manager
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

46Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
1.5/2.5CI-Tests — 9 out of 15 merged PRs checked by a CI test -- score normalized to 6
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 1/18 approved changesets -- score normalized to 0
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 30 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
1.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 21 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate4
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
6.2/25Indirect dependencies free of known advisories — 3 affected: adm-zip 0.5.18 (high 7.5), sharp 0.34.5 (high 8.4), sprintf-js 1.1.3 (moderate 5.3)
28.6/40No advisories left outstanding — 2 advisory-carrying package(s) unaddressed past 90 days; oldest published 103 days ago
Inputs used
sourceosv
advisories12
affected_packages3
assessed_packages148
unassessed_packages0
affected_by_severityhigh 2, moderate 1
direct_affected_packages0
Matched the npm:akm-cli@0.9.32 runtime dependency closure — what installing the published package pulls in — 148 packages. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

82Excellent · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, src/assets/stash-skeleton/facts/conventions/assets/agent.md, tests/fixtures/bundles/claude/CLAUDE.md, tests/fixtures/bundles/opencode/AGENTS.md, tests/fixtures/execution-contracts/native/claude/CLAUDE.md, tests/fixtures/execution-contracts/native/opencode/AGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 93 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.93
agent_instruction_filesAGENTS.md, src/assets/stash-skeleton/facts/conventions/assets/agent.md, tests/fixtures/bundles/claude/CLAUDE.md, tests/fixtures/bundles/opencode/AGENTS.md, tests/fixtures/execution-contracts/native/claude/CLAUDE.md, tests/fixtures/execution-contracts/native/opencode/AGENTS.md
agent_instruction_max_bytes18,600
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — biome.json
11/11Static type checking — tsconfig.json
10/10Reproducible environment — Dockerfile
10/10Demonstrated agent practice — 97 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
3/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0.97
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54.4/55Manageable file sizes — 16/1,554 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes114,322
source_files_sampled1,554
oversized_source_files16
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
20/20MCP server
40/40Runnable examples — recipes
Inputs used
example_dirsrecipes
has_mcp_signalyes
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

66GitHub stars
5contributors
5,351commits, last 12 months
0days since last push
100releases
1bus factor
19open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 4 ⇿
0Stars
4Forks
84Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

1223344412026-032026-072026-10
Major 0Minor 1Patch 31
OpenSSF Scorecard 4.0 / 10
4.0aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-10-22 07:48 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
6CI-Tests9 out of 15 merged PRs checked by a CI test -- score normalized to 6
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/18 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 30 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities21 existing vulnerabilities detected
Direct dependencies 11
RegistryPackageVersion constraintManifest
npm@clack/prompts^1.3.0package.json
npm@huggingface/transformers4.2.0package.json
npm@opencode-ai/sdk1.2.20package.json
npmcitty^0.2.2package.json
npmdotenv^17.4.2package.json
npmfast-xml-parser^5.10.1package.json
npmnode-html-parser^9.0.1package.json
npmsemver^7.6.0package.json
npmturndown^7.2.4package.json
npmyaml^2.8.4package.json
npmzod^3.23.0package.json
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

Dependency advisories 3

Installing npm:akm-cli@0.9.32 pulls in 148 packages, direct and transitive: 3 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
adm-zip0.5.18indirecthigh80.6.1
sharp0.34.5indirecthigh30.35.5
sprintf-js1.1.3indirectmoderate1—

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — npm.