Public record
Software health reportschema 0.27.0 · metrics 2.10.0 · 2026-08-01 22:40 UTC

DaniAkash / agent-toolkit

Tooling for AI coding agents. Vercel AI SDK adapters, sandbox providers, skill and MCP managers, ACP-protocol utilities.

TypeScriptMIT★ 2 stars⑂ 1 forksince May 2026View on GitHub ↗
KindLibraryMCP serverhow this is determined

DaniAkash/agent-toolkit holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (73/100) and lowest on Community & Adoption (41/100). It was last updated 8 days ago. A single contributor accounts for most of its recent work.

63
overall / 100
Moderate

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.

63
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 59 is calibrated to 63 on the published index scale (record calibration 2026-08-02).

Ownership

Dani AkashPersonal account
244 followers180 public repossince Mar 2014https://github.com/browseros-ai

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?

72Good · 21% of overall
How it's scored
28.8/36Push recencylast push 8 days ago
6.2/36Commit cadence9/52 weeks with commits
18/18Commit volume196 commits in the last year
0/10OpenSSF Scorecard: Maintainedproject was created within the last 90 days. Please review its contents carefully
Inputs used
commits_last_year196
human_commit_share1
days_since_last_push8
active_weeks_last_year9

Release discipline

100Exceptional
How it's scored
27/27Ships releases14 releases published
36/36Release recencylatest release 8 days ago
27/27Release cadencea release every ~8.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count14
latest_release_tagagent-mcp-manager-v0.1.0
releases_from_tagsno
days_since_latest_release8
mean_days_between_releases8.1
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

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

41Weak · 17% of overall
How it's scored
0/60Stars2 stars
0/25Forks1 forks
0/15Watchers0 watchers
Inputs used
forks1
stars2
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
51.7/80Monthly downloads7,486 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesagent-mcp-manager
dependents
ecosystemsnpm
total_downloads
monthly_downloads7,486
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?

62Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.1/22.5Commit distributiontop contributor authored 100% of commits
2.7/13.5Contributor breadth2 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.995
How it's scored
42/42Issue resolution100% of issues closed
29.4/30PR acceptance53/54 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/3 approved changesets -- score normalized to 0
Inputs used
merged_prs53
open_issues0
closed_issues9
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs1
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
17.2/25Owner reach244 followers of DaniAkash
25/25Track record180 public repos, account ~12 yr old
Inputs used
followers244
owner_typeUser
is_verified
owner_loginDaniAkash
public_repos180
account_age_days4,534
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 9 days ago
20/20Version history8 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesagent-mcp-manager
ecosystemsnpm
any_deprecatedno
min_days_since_publish9

Engineering Quality

Are baseline engineering and documentation practices in place?

73Good · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter configbiome.json
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
12/20OpenSSF Scorecard: CI-Tests2 out of 3 merged PRs checked by a CI test -- score normalized to 6
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics11 topics
10/10Wiki
Inputs used
topicsacp, agent-client-protocol, ai-coding-agents, claude-code, codex, gemini, mcp, model-context-protocol, monorepo, typescript, vercel-ai-sdk
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

44Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
1.5/2.5CI-Tests2 out of 3 merged PRs checked by a CI test -- score normalized to 6
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/3 approved changesets -- score normalized to 0
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintainedproject was created within the last 90 days. Please review its contents carefully
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
1.5/7.5Vulnerabilities8 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate3
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages1
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:acp-probe@0.0.2 runtime dependency closure — what installing the published package pulls in — 1 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.

50Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share1
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configbiome.json
11/11Static type checkingpackages/acp-probe/tsconfig.json, packages/acpx-ai-harness/tsconfig.json, packages/acpx-ai-provider/tsconfig.json, packages/acpx-test-helpers/tsconfig.json, packages/agent-mcp-manager/tsconfig.json, packages/agent-skills-manager/tsconfig.json, packages/ai-sdk-microsandbox/tsconfig.json, tsconfig.json
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configspackages/acp-probe/tsconfig.json, packages/acpx-ai-harness/tsconfig.json, packages/acpx-ai-provider/tsconfig.json, packages/acpx-test-helpers/tsconfig.json, packages/agent-mcp-manager/tsconfig.json, packages/agent-skills-manager/tsconfig.json, packages/ai-sdk-microsandbox/tsconfig.json, tsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/198 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes24,405
source_files_sampled198
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs
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

2GitHub stars
2contributors
196commits, last 12 months
8days since last push
14releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • npm package 'acp-probe' points at a different repository (https://github.com/DaniAkash/acpx); excluded from ecosystem scoring
  • npm package 'acpx-ai-harness' points at a different repository (https://github.com/DaniAkash/acpx); excluded from ecosystem scoring
  • npm package 'acpx-ai-provider' points at a different repository (https://github.com/DaniAkash/acpx); excluded from ecosystem scoring
  • npm package 'ai-sdk-microsandbox' points at a different repository (https://github.com/DaniAkash/acpx); excluded from ecosystem scoring
  • npm package 'agent-skills-manager' points at a different repository (https://github.com/DaniAkash/acpx); excluded from ecosystem scoring

More detail

OpenSSF Scorecard 3.0 / 10
3.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-08-01 22:39 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
6CI-Tests2 out of 3 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 0/3 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
0Maintainedproject was created within the last 90 days. Please review its contents carefully
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
2Vulnerabilities8 existing vulnerabilities detected
Direct dependencies 8
RegistryPackageVersion constraintManifest
npm@agentclientprotocol/sdk^0.21.0packages/acp-probe/package.json
npmws^8.20.1packages/acpx-ai-harness/package.json
npmzod3.25.76packages/acpx-ai-harness/package.json
npm@iarna/toml^2.2.5packages/agent-mcp-manager/package.json
npmjsonc-parser^3.3.1packages/agent-mcp-manager/package.json
npmyaml^2.9.0packages/agent-mcp-manager/package.json
npmxdg-basedir^5.1.0packages/agent-skills-manager/package.json
npmyaml^2.8.3packages/agent-skills-manager/package.json
All dependencies 30

Full resolved dependency set from the GitHub dependency graph: 10 direct and 20 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
npm@agentclientprotocol/sdk^0.21.0direct
npm@iarna/toml^2.2.5direct
npmjsonc-parser^3.3.1direct
npmws8.21.0direct
npmws^8.20.1direct
npmxdg-basedir^5.1.0direct
npmyaml^2.8.3direct
npmyaml^2.9.0direct
npmzod3.25.76direct
npmzod^4.4.3direct
npm@ai-sdk/harness1.0.0-canary.10indirect
npm@ai-sdk/harness1.0.0-canary.13indirect
npm@ai-sdk/harness-codex1.0.0-canary.9indirect
npm@ai-sdk/provider4.0.0-beta.14indirect
npm@ai-sdk/provider4.0.0-canary.18indirect
npm@ai-sdk/provider-utils5.0.0-beta.30indirect
npm@ai-sdk/provider-utils5.0.0-canary.48indirect
npm@ai-sdk/sandbox-vercel1.0.0-canary.10indirect
npm@biomejs/biome^2.4.14indirect
npm@modelcontextprotocol/sdk1.29.0indirect
npm@types/bun^1.3.13indirect
npm@types/ws^8indirect
npmacpx0.8.0indirect
npmacpx^0.7.0indirect
npmacpx^0.8.0indirect
npmai7.0.0-beta.116indirect
npmbunup^0.16.31indirect
npmfallow^2.63.0indirect
npmmicrosandbox0.5.7indirect
npmtypescript^6.0.3indirect
Dependency advisories 0

Installing npm:acp-probe@0.0.2 pulls in 1 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

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.27.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.