Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-21 06:32 UTC

inspect-js / node-deep-equal

node's assert.deepEqual algorithm

JavaScriptMIT★ 792 stars⑂ 106 forkssince Feb 2012View on GitHub ↗

inspect-js/node-deep-equal holds a health index of 56 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (83/100) and lowest on Vitality (21/100). It was last updated 219 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Inspect JSOrganization
53 followers83 public repossince Aug 2019

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmdeep-equal2.2.3124,622,236221077 days agoequalityequalcompare

Metrics by category

Vitality

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

21At Risk · 21% of overall
How it's scored
3.6/36Push recency — last push 219 days ago
1.4/36Commit cadence — 2/52 weeks with commits
7.6/18Commit volume — 6 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year6
human_commit_share1
days_since_last_push219
active_weeks_last_year2
How it's scored
16.2/27Ships releases — 23 version tags (no GitHub releases)
0/36Release recency — latest release 1,077 days ago
12.6/27Release cadence — a release every ~159 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count23
latest_release_tagv2.2.3
releases_from_tagsyes
days_since_latest_release1,077
mean_days_between_releases159
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?

83Excellent · 17% of overall
How it's scored
47/60Stars — 792 stars
16.8/25Forks — 106 forks
6.2/15Watchers — 14 watchers
Inputs used
forks106
stars792
watchers14
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/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_conductyes
readme_badge_services—
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 124,622,236 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesdeep-equal
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads124,622,236
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?

56Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.7/22.5Commit distribution — top contributor authored 92% of commits
13.5/13.5Contributor breadth — 15 contributors
10/10OpenSSF Scorecard: Contributors — project has 31 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled15
top_contributor_share0.925
How it's scored
39.1/42Issue resolution — 93% of issues closed
13/30PR acceptance — 23/53 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs23
open_issues4
closed_issues53
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.93
closed_unmerged_prs30
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
30/30Ownership backing — organization-owned
0/20Verified domain
12.5/25Owner reach — 53 followers of inspect-js
25/25Track record — 83 public repos, account ~7 yr old
Inputs used
followers53
owner_typeOrganization
is_verifiedno
owner_logininspect-js
public_repos83
account_age_days2,625
How it's scored
25/25Published & resolvable — 1 package(s) on npm
4/35Publish recency — latest publish 1,077 days ago
20/20Version history — 22 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesdeep-equal
ecosystemsnpm
any_deprecatedno
min_days_since_publish1,077

Engineering Quality

Are baseline engineering and documentation practices in place?

68Good · 19% of overall
How it's scored
24/24CI workflows — 6 workflow(s)
24/24Tests present
16/16Linter config — .eslintrc
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 8 topics
0/10Wiki
Inputs used
topicsdeepequal, equal, node, javascript, nodejs, assert, strict, loose
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?

54Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 31 contributing companies or organizations
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
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — no SAST tool detected
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate4.2
Excluded from scoring (no data or not applicable): Branch-Protection, CI-Tests, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages61
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:deep-equal@2.2.3 runtime dependency closure — what installing the published package pulls in — 61 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.

37Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
1.6/40Legible commit history — 3 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.03
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .eslintrc
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/5 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes33,346
source_files_sampled5
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — example
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

792GitHub stars
15contributors
6commits, last 12 months
219days since last push
23releases
1bus factor
4open 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 ★ / 106 ⇿
0Stars
106Forks
22Releases

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.

0204060801009832013-012019-102026-07
Major 2Minor 5Patch 15

Each point covers 13 days.

OpenSSF Scorecard 4.2 / 10
4.2aggregate

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-21 06:32 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 31 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTno SAST tool detected
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 18
RegistryPackageVersion constraintManifest
npmarray-buffer-byte-length^1.0.2package.json
npmcall-bound^1.0.4package.json
npmes-get-iterator^1.1.3package.json
npmget-intrinsic^1.3.0package.json
npmis-arguments^1.2.0package.json
npmis-array-buffer^3.0.5package.json
npmis-date-object^1.1.0package.json
npmis-regex^1.2.1package.json
npmis-shared-array-buffer^1.0.4package.json
npmisarray^2.0.5package.json
npmobject-is^1.1.6package.json
npmobject-keys^1.1.1package.json
npmobject.assign^4.1.7package.json
npmregexp.prototype.flags^1.5.4package.json
npmside-channel^1.1.0package.json
npmwhich-boxed-primitive^1.1.1package.json
npmwhich-collection^1.0.2package.json
npmwhich-typed-array^1.1.20package.json
All dependencies 34

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

RegistryPackageVersionRelation
npmarray-buffer-byte-length^1.0.2direct
npmcall-bound^1.0.4direct
npmes-get-iterator^1.1.3direct
npmget-intrinsic^1.3.0direct
npmis-arguments^1.2.0direct
npmis-array-buffer^3.0.5direct
npmis-date-object^1.1.0direct
npmis-regex^1.2.1direct
npmis-shared-array-buffer^1.0.4direct
npmisarray^2.0.5direct
npmobject-is^1.1.6direct
npmobject-keys^1.1.1direct
npmobject.assign^4.1.7direct
npmregexp.prototype.flags^1.5.4direct
npmside-channel^1.1.0direct
npmwhich-boxed-primitive^1.1.1direct
npmwhich-collection^1.0.2direct
npmwhich-typed-array^1.1.20direct
npm@ljharb/eslint-config^22.2.0indirect
npmauto-changelog^2.5.0indirect
npmavailable-typed-arrays^1.0.7indirect
npmencoding^0.1.13indirect
npmeslint^8.57.1indirect
npmfor-each^0.3.5indirect
npmhas-proto^1.2.0indirect
npmhas-symbols^1.1.0indirect
npmhas-typed-arrays^1.1.0indirect
npmin-publish^2.0.1indirect
npmnpmignore^0.3.5indirect
npmnyc^10.3.2indirect
npmobject.getownpropertydescriptors^2.1.9indirect
npmsafe-publish-latest^2.0.0indirect
npmsemver^6.3.1indirect
npmtape^5.9.0indirect
Dependency advisories 0

Installing npm:deep-equal@2.2.3 pulls in 61 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.34.0 — full methodology · metrics wiki.

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