Public record
Software health reportschema 0.30.0 · metrics 2.10.0 · 2026-08-04 17:43 UTC

juliangruber / isarray

Array#isArray for older browsers.

JavaScriptMIT★ 132 stars⑂ 44 forkssince May 2013View on GitHub ↗

juliangruber/isarray holds a health index of 65 out of 100, placing it in the Good band. It scores highest on Security (74/100) and lowest on AI Readiness (43/100). It was last updated 14 days ago. A single contributor accounts for most of its recent work.

65
overall / 100
Good

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.

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

Ownership

Julian GruberPersonal account
1,733 followers815 public repossince May 2008@socketdev

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmisarray2.0.5985,692,47392584 days agobrowserisarrayarray

Metrics by category

Vitality

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

48Weak · 21% of overall
How it's scored
28.8/36Push recencylast push 14 days ago
8.3/36Commit cadence12/52 weeks with commits
10.3/18Commit volume13 commits in the last year
3/10OpenSSF Scorecard: Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
Inputs used
commits_last_year13
human_commit_share0.57
days_since_last_push14
active_weeks_last_year12
How it's scored
27/27Ships releases1 releases published
0/36Release recencylatest release 2,467 days ago
12.6/27Release cadencecadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count1
latest_release_tagv2.0.5
releases_from_tagsno
days_since_latest_release2,467
mean_days_between_releases
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?

71Good · 17% of overall
How it's scored
34.3/60Stars132 stars
13.6/25Forks44 forks
5/15Watchers9 watchers
Inputs used
forks44
stars132
watchers9
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_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesapi.securityscorecards.dev, shields.io, www.bestpractices.dev
has_pull_request_templateno
How it's scored
80/80Monthly downloads985,692,473 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesisarray
dependents
ecosystemsnpm
total_downloads
monthly_downloads985,692,473
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?

65Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
5/22.5Commit distributiontop contributor authored 78% of commits
13.5/13.5Contributor breadth13 contributors
10/10OpenSSF Scorecard: Contributorsproject has 17 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled13
top_contributor_share0.776
How it's scored
39.2/42Issue resolution93% of issues closed
20.9/30PR acceptance67/96 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Reviewall changesets reviewed
Inputs used
merged_prs67
open_issues1
closed_issues14
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.933
closed_unmerged_prs29
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 backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
23.3/25Owner reach1,733 followers of juliangruber
25/25Track record815 public repos, account ~18 yr old
Inputs used
followers1,733
owner_typeUser
is_verified
owner_loginjuliangruber
public_repos815
account_age_days6,656
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on npm
4/35Publish recencylatest publish 2,584 days ago
20/20Version history9 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesisarray
ecosystemsnpm
any_deprecatedno
min_days_since_publish2,584

Engineering Quality

Are baseline engineering and documentation practices in place?

49Weak · 19% of overall
How it's scored
24/24CI workflows5 workflow(s)
0/24Tests present
16/16Linter config.eslintrc
0/9.6Pre-commit hooks
0/6.4.editorconfig
8/20OpenSSF Scorecard: CI-Tests13 out of 29 merged PRs checked by a CI test -- score normalized to 4
Inputs used
has_ciyes
has_testsno
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
0/10Topics
10/10Wiki
Inputs used
topics
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?

74Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
1/2.5CI-Tests13 out of 29 merged PRs checked by a CI test -- score normalized to 4
1.2/2.5CII-Best-Practicesbadge detected: Passing
7.5/7.5Code-Reviewall changesets reviewed
2.5/2.5Contributorsproject has 17 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
2.2/7.5Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
0/5Packagingno data
2/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
1.5/7.5Vulnerabilities8 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.8
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, 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
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories8
affected_packages4
assessed_packages150
unassessed_packages0
affected_by_severityhigh 3, moderate 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 150 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

43Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
26.2/40Legible commit history28 of 57 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.491
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapMakefile
0/22Automated tests
11/11Lint / format config.eslintrc
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance43 of the last 100 commits are automated dependency updates
4/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
Inputs used
has_nixno
has_testsno
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.43
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
55/55Manageable file sizes0/2 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes1,162
source_files_sampled2
oversized_source_files0

Key facts

132GitHub stars
13contributors
13commits, last 12 months
14days since last push
1releases
1bus factor
1open 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 ★ / 44 ⇿
0Stars
44Forks
1Releases

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.

010203040504352015-082021-012026-06
Major 0Minor 0Patch 1

Each point covers 10 days.

OpenSSF Scorecard 6.8 / 10
6.8aggregate

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-04 17:43 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
4CI-Tests13 out of 29 merged PRs checked by a CI test -- score normalized to 4
5CII-Best-Practicesbadge detected: Passing
10Code-Reviewall changesets reviewed
10Contributorsproject has 17 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
3Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
n/aPackagingpackaging workflow not detected
4Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 4
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
2Vulnerabilities8 existing vulnerabilities detected
All dependencies 150

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

RegistryPackageVersionRelation
npm@eslint/eslintrc1.3.0indirect
npm@eslint/eslintrc3.3.1indirect
npm@humanwhocodes/config-array0.9.5indirect
npm@humanwhocodes/object-schema1.2.1indirect
npm@ljharb/eslint-config22.0.0indirect
npmacorn8.15.0indirect
npmacorn-jsx5.3.2indirect
npmajv6.12.6indirect
npmansi-regex5.0.1indirect
npmansi-styles4.3.0indirect
npmargparse2.0.1indirect
npmarray.prototype.every1.1.3indirect
npmavailable-typed-arrays1.0.5indirect
npmbalanced-match1.0.2indirect
npmbrace-expansion1.1.11indirect
npmcall-bind1.0.2indirect
npmcallsites3.1.0indirect
npmchalk4.1.2indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmconcat-map0.0.1indirect
npmcross-spawn7.0.3indirect
npmdebug4.3.4indirect
npmdeep-equal2.0.5indirect
npmdeep-is0.1.4indirect
npmdefine-properties1.1.4indirect
npmdefined1.0.0indirect
npmdoctrine3.0.0indirect
npmdotignore0.1.2indirect
npmes-abstract1.20.1indirect
npmes-get-iterator1.1.2indirect
npmes-to-primitive1.2.1indirect
npmescape-string-regexp4.0.0indirect
npmeslint8.8.0indirect
npmeslint-scope7.1.0indirect
npmeslint-utils3.0.0indirect
npmeslint-visitor-keys2.1.0indirect
npmeslint-visitor-keys3.3.0indirect
npmeslint-visitor-keys4.2.1indirect
npmespree10.4.0indirect
npmespree9.3.2indirect
npmesquery1.4.0indirect
npmesrecurse4.3.0indirect
npmestraverse5.3.0indirect
npmesutils2.0.3indirect
npmfast-deep-equal3.1.3indirect
npmfast-json-stable-stringify2.1.0indirect
npmfast-levenshtein2.0.6indirect
npmfile-entry-cache6.0.1indirect
npmflat-cache3.0.4indirect
npmflatted3.4.2indirect
npmfor-each0.3.3indirect
npmfs.realpath1.0.0indirect
npmfunction-bind1.1.1indirect
npmfunction.prototype.name1.1.5indirect
npmfunctional-red-black-tree1.0.1indirect
npmfunctions-have-names1.2.3indirect
npmget-intrinsic1.1.2indirect
npmget-package-type0.1.0indirect
npmget-symbol-description1.0.0indirect
npmglob7.2.3indirect
npmglob-parent6.0.2indirect
npmglobals13.17.0indirect
npmglobals14.0.0indirect
npmhas1.0.3indirect
npmhas-bigints1.0.2indirect
npmhas-dynamic-import2.0.1indirect
npmhas-flag4.0.0indirect
npmhas-property-descriptors1.0.0indirect
npmhas-symbols1.0.3indirect
npmhas-tostringtag1.0.0indirect
npmignore5.2.0indirect
npmimport-fresh3.3.0indirect
npmimurmurhash0.1.4indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npminternal-slot1.0.3indirect
npmis-arguments1.1.1indirect
npmis-bigint1.0.4indirect
npmis-boolean-object1.1.2indirect
npmis-callable1.2.4indirect
npmis-core-module2.9.0indirect
npmis-date-object1.0.5indirect
npmis-extglob2.1.1indirect
npmis-glob4.0.3indirect
npmis-map2.0.2indirect
npmis-negative-zero2.0.2indirect
npmis-number-object1.0.7indirect
npmis-regex1.1.4indirect
npmis-set2.0.2indirect
npmis-shared-array-buffer1.0.2indirect
npmis-string1.0.7indirect
npmis-symbol1.0.4indirect
npmis-typed-array1.1.9indirect
npmis-weakmap2.0.1indirect
npmis-weakref1.0.2indirect
npmis-weakset2.0.2indirect
npmisarray2.0.5indirect
npmisexe2.0.0indirect
npmjs-yaml4.2.0indirect
npmjson-schema-traverse0.4.1indirect
npmjson-stable-stringify-without-jsonify1.0.1indirect
npmlevn0.4.1indirect
npmlodash.merge4.6.2indirect
npmminimatch3.1.5indirect
npmminimist1.2.6indirect
npmms2.1.2indirect
npmnatural-compare1.4.0indirect
npmobject-inspect1.12.2indirect
npmobject-is1.1.5indirect
npmobject-keys1.1.1indirect
npmobject.assign4.1.4indirect
npmonce1.4.0indirect
npmoptionator0.9.1indirect
npmparent-module1.0.1indirect
npmpath-is-absolute1.0.1indirect
npmpath-key3.1.1indirect
npmpath-parse1.0.7indirect
npmprelude-ls1.2.1indirect
npmpunycode2.1.1indirect
npmregexp.prototype.flags1.4.3indirect
npmregexpp3.2.0indirect
npmresolve2.0.0-next.4indirect
npmresolve-from4.0.0indirect
npmresumer0.0.0indirect
npmrimraf3.0.2indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmside-channel1.0.4indirect
npmstring.prototype.trim1.2.6indirect
npmstring.prototype.trimend1.0.5indirect
npmstring.prototype.trimstart1.0.5indirect
npmstrip-ansi6.0.1indirect
npmstrip-json-comments3.1.1indirect
npmsupports-color7.2.0indirect
npmsupports-preserve-symlinks-flag1.0.0indirect
npmtape5.6.1indirect
npmtext-table0.2.0indirect
npmthrough2.3.8indirect
npmtype-check0.4.0indirect
npmtype-fest0.20.2indirect
npmunbox-primitive1.0.2indirect
npmuri-js4.4.1indirect
npmv8-compile-cache2.3.0indirect
npmwhich2.0.2indirect
npmwhich-boxed-primitive1.0.2indirect
npmwhich-collection1.0.1indirect
npmwhich-typed-array1.1.8indirect
npmword-wrap1.2.4indirect
npmwrappy1.0.2indirect
Dependency advisories 4

This repository publishes no package the index resolves, so its own dependency graph was assessed — 150 packages, which also include development and test pins that never ship: 4 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
brace-expansion1.1.11indirecthigh55.0.9
cross-spawn7.0.3indirecthigh17.0.5
js-yaml4.2.0indirecthigh14.3.0
ajv6.12.6indirectmoderate18.18.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.30.0 — full methodology · metrics wiki.

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