Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-20 08:06 UTC

readmeio / api-explorer

Open source components that make up ReadMe's legacy API explorer

JavaScript · CSSMIT★ 84 stars⑂ 24 forkssince Jul 2017archivedView on GitHub ↗

readmeio/api-explorer holds a health index of 19 out of 100, placing it in the Critical band. It scores highest on Sustainability & Governance (64/100) and lowest on Vitality (20/100). The repository is archived, so no further maintenance is expected.

19
overall / 100
Critical

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.

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

Ownership

ReadMeOrganization · verified domain
260 followers108 public repossince Mar 2014

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@readme/api-logs⚠ This package is no longer maintained.13.4.91471021926 days ago
npm@readme/oas-form⚠ This package is no longer supported.13.4.9111321926 days agoreactformjson-schema
npm@readme/api-explorer⚠ This package is no longer maintained.13.4.183932781901 days ago

Metrics by category

Vitality

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

20At Risk · 21% of overall
How it's scored
0/36Push recencylast push 1,744 days ago
0/36Commit cadence0/52 weeks with commits
0/18Commit volume0 commits in the last year
0/10OpenSSF Scorecard: Maintainedproject is archived
Inputs used
commits_last_year0
human_commit_share0.69
days_since_last_push1,744
active_weeks_last_year0
How it's scored
16.2/27Ships releases100 version tags (no GitHub releases)
0/36Release recencylatest release 1,901 days ago
27/27Release cadencea release every ~2.8 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv13.4.18
releases_from_tagsyes
days_since_latest_release1,901
mean_days_between_releases2.8
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?

63Moderate · 17% of overall
How it's scored
31.1/60Stars84 stars
11.3/25Forks24 forks
5/15Watchers9 watchers
Inputs used
forks24
stars84
watchers9
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com
has_pull_request_templateyes
How it's scored
37.5/80Monthly downloads651 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@readme/api-logs, @readme/oas-form, @readme/api-explorer
dependents
ecosystemsnpm
total_downloads
monthly_downloads651
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?

64Moderate · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
11.7/22.5Commit distributiontop contributor authored 48% of commits
13.5/13.5Contributor breadth20 contributors
10/10OpenSSF Scorecard: Contributorsproject has 10 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled20
top_contributor_share0.481
How it's scored
0/42Issue resolutionno issues or no data
22.5/30PR acceptance875/1,166 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 4/29 approved changesets -- score normalized to 1
Inputs used
merged_prs875
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio
closed_unmerged_prs291
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
17.4/25Owner reach260 followers of readmeio
25/25Track record108 public repos, account ~12 yr old
Inputs used
followers260
owner_typeOrganization
is_verifiedyes
owner_loginreadmeio
public_repos108
account_age_days4,580
How it's scored
25/25Published & resolvable3 package(s) on npm
4/35Publish recencylatest publish 1,901 days ago
20/20Version history278 published versions
0/20Not deprecated@readme/api-logs: This package is no longer maintained.
Inputs used
packages@readme/api-logs, @readme/oas-form, @readme/api-explorer
ecosystemsnpm
any_deprecatedyes
min_days_since_publish1,901

Engineering Quality

Are baseline engineering and documentation practices in place?

58Moderate · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter config.eslintrc, package.json ("prettier"), packages/api-explorer/package.json ("prettier"), packages/api-logs/package.json ("prettier"), packages/oas-form/package.json ("prettier")
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 13 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics2 topics
0/10Wiki
Inputs used
topicsopenapi, react
has_wikino
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?

45Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
3.8/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
0/2.5CI-Tests0 out of 13 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 4/29 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 10 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintainedproject is archived
0/5Packagingno data
0.5/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
3.5/5SASTSAST tool detected but not run on all commits
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities216 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.7
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
14/35Direct dependencies free of known advisories1 affected: js-cookie 2.2.1 (high 7.5)
5.4/25Indirect dependencies free of known advisories6 affected: form-data 3.0.0 (high 7.5), minimatch 4.2.3 (high 7.5), trim 0.0.1 (high 7.5), +3 more
18.1/40No advisories left outstanding7 advisory-carrying package(s) unaddressed past 90 days; oldest published 1,958 days ago
Inputs used
sourceosv
advisories12
affected_packages7
assessed_packages532
unassessed_packages0
affected_by_severityhigh 5, moderate 2
direct_affected_packages1
Matched the npm:@readme/api-explorer@13.4.18 runtime dependency closure — what installing the published package pulls in — 532 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.

54Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
34/40Legible commit history44 of 69 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.638
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.eslintrc, package.json ("prettier"), packages/api-explorer/package.json ("prettier"), packages/api-logs/package.json ("prettier"), packages/oas-form/package.json ("prettier")
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance31 of the last 100 commits are automated dependency updates
1/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.31
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
54.7/55Manageable file sizes1/169 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes65,344
source_files_sampled169
oversized_source_files1
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexample
Inputs used
example_dirsexample
has_mcp_signalno
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

84GitHub stars
20contributors
0commits, last 12 months
1,744days since last push
100releases
2bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 24 ⇿
0Stars
24Forks
100Releases

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.

048121620242422018-052022-032026-01
Major 7Minor 23Patch 69

Each point covers 7 days.

OpenSSF Scorecard 4.7 / 10
4.7aggregate

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-09-20 08:06 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests0 out of 13 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 4/29 approved changesets -- score normalized to 1
10Contributorsproject has 10 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintainedproject is archived
n/aPackagingpackaging workflow not detected
1Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 1
7SASTSAST tool detected but not run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities216 existing vulnerabilities detected
Direct dependencies 37
RegistryPackageVersion constraintManifest
npm@apidevtools/swagger-parser^10.0.1package.json
npm@readme/emojis^3.0.0package.json
npm@readme/oas-extensions^13.5.0package.json
npm@readme/ui^1.17.8package.json
npmbabel-polyfill^6.26.0package.json
npmoas^13.0.4package.json
npmprop-types^15.7.2package.json
npmreact-hot-loader^4.12.16package.json
npmswagger2openapi^7.0.0package.json
npmwhatwg-fetch^3.0.0package.json
npmyaml^1.8.3package.json
npm@readme/http-status-codes^7.1.0packages/api-explorer/package.json
npm@readme/markdown-magic^11.0.0packages/api-explorer/package.json
npm@readme/oas-extensions^13.5.0packages/api-explorer/package.json
npm@readme/oas-formfile:../oas-formpackages/api-explorer/package.json
npm@readme/oas-to-har^13.5.0packages/api-explorer/package.json
npm@readme/oas-to-snippet^13.5.2packages/api-explorer/package.json
npm@readme/syntax-highlighter^10.10.1packages/api-explorer/package.json
npm@readme/variable^13.5.1packages/api-explorer/package.json
npmclassnames^2.2.5packages/api-explorer/package.json
npmfetch-har^4.0.2packages/api-explorer/package.json
npmjs-cookie^2.1.4packages/api-explorer/package.json
npmlodash.clonedeep^4.5.0packages/api-explorer/package.json
npmlodash.kebabcase^4.1.1packages/api-explorer/package.json
npmoas^13.0.4packages/api-explorer/package.json
npmprop-types^15.7.2packages/api-explorer/package.json
npmreact-copy-to-clipboard^5.0.1packages/api-explorer/package.json
npmreact-debounce-input^3.2.0packages/api-explorer/package.json
npmreact-json-view^1.21.1packages/api-explorer/package.json
npmreact-waypoint^9.0.2packages/api-explorer/package.json
npmwhatwg-fetch^3.0.0packages/api-explorer/package.json
npmasync-retry^1.2.3packages/api-logs/package.json
npmprop-types^15.7.2packages/api-logs/package.json
npmjson-schema-merge-allof^0.6.0packages/oas-form/package.json
npmjsonpointer^4.0.1packages/oas-form/package.json
npmnanoid^3.1.20packages/oas-form/package.json
npmprop-types^15.7.2packages/oas-form/package.json
All dependencies 0

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

RegistryPackageVersionRelation
Dependency advisories 7

Installing npm:@readme/api-explorer@13.4.18 pulls in 532 packages, direct and transitive: 7 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
js-cookie2.2.1directhigh13.0.7
form-data3.0.0indirecthigh24.0.6
minimatch4.2.3indirecthigh310.2.3
trim0.0.1indirecthigh10.0.3
ws8.13.0indirecthigh38.21.0
codemirror5.54.0indirectmoderate15.58.2
jsonpointer4.1.0indirectmoderate15.0.0

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 statisticsnpm.