Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-20 19:39 UTC

Netflix / unleash

Professionally publish your JavaScript modules in one keystroke

JavaScriptApache-2.0★ 597 stars⑂ 27 forkssince Mar 2016View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

Netflix/unleash holds a health index of 23 out of 100, placing it in the At Risk band. It scores highest on Community & Adoption (58/100) and lowest on Vitality (20/100). It was last updated 1254 days ago. A single contributor accounts for most of its recent work.

23
overall / 100
At Risk

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.

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

Ownership

Netflix, Inc.Organization
10,273 followers239 public repossince Jul 2011

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmunleash2.0.2880272333 days agogithubreleaseshipcoderelease-itdry-runshipitreleaseitgitprocesstoolnpmdeploydeploymentpublishpushghpagesruntests

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 recency — last push 1,254 days ago
0/36Commit cadence — 0/52 weeks with commits
0/18Commit volume — 0 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_year0
human_commit_share1
days_since_last_push1,254
active_weeks_last_year0
How it's scored
16.2/27Ships releases — 26 version tags (no GitHub releases)
0/36Release recency — latest release 3,235 days ago
27/27Release cadence — a release every ~1.7 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count26
latest_release_tagv2.0.1
releases_from_tagsyes
days_since_latest_release3,235
mean_days_between_releases1.7
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?

58Moderate · 17% of overall
How it's scored
45/60Stars — 597 stars
11.8/25Forks — 27 forks
14.2/15Watchers — 358 watchers
Inputs used
forks27
stars597
watchers358
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicestravis-ci.org
has_pull_request_templateno
How it's scored
39.3/80Monthly downloads — 880 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesunleash
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads880
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?

57Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
11.2/22.5Commit distribution — top contributor authored 50% of commits
4.1/13.5Contributor breadth — 3 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.5
How it's scored
22.2/42Issue resolution — 53% of issues closed
30/30PR acceptance — 5/5 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 1/14 approved changesets -- score normalized to 0
Inputs used
merged_prs5
open_issues8
closed_issues9
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.529
closed_unmerged_prs0
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
25/25Owner reach — 10,273 followers of Netflix
25/25Track record — 239 public repos, account ~15 yr old
Inputs used
followers10,273
owner_typeOrganization
is_verifiedno
owner_loginNetflix
public_repos239
account_age_days5,547
How it's scored
25/25Published & resolvable — 1 package(s) on npm
4/35Publish recency — latest publish 2,333 days ago
20/20Version history — 27 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesunleash
ecosystemsnpm
any_deprecatedno
min_days_since_publish2,333

Engineering Quality

Are baseline engineering and documentation practices in place?

50Moderate · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter config — .eslintrc
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 2 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — http://netflix.github.io/unleash/
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepagehttp://netflix.github.io/unleash/
docs_sitehttp://netflix.github.io/unleash/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

28At Risk · 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
0/2.5CI-Tests — 0 out of 2 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 1/14 approved changesets -- score normalized to 0
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
0/10Dangerous-Workflow — no data
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 — no data
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate2.6
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.
How it's scored
14/35Direct dependencies free of known advisories — 1 affected: semver 5.0.3 (high 7.5)
4.8/25Indirect dependencies free of known advisories — 8 affected: braces 1.8.5 (high 7.5), cross-spawn 5.1.0 (high 7.5), lodash.template 3.6.2 (high 7.2), +5 more
16.1/40No advisories left outstanding — 9 advisory-carrying package(s) unaddressed past 90 days; oldest published 2,633 days ago
Inputs used
sourceosv
advisories9
affected_packages9
assessed_packages771
unassessed_packages0
affected_by_severityhigh 5, moderate 4
direct_affected_packages1
Matched the npm:unleash@2.0.2 runtime dependency closure — what installing the published package pulls in — 771 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.

41Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 99 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.99
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 — no data
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
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/11 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes9,030
source_files_sampled11
oversized_source_files0

Key facts

597GitHub stars
3contributors
0commits, last 12 months
1,254days since last push
26releases
1bus factor
8open 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 ★ / 27 ⇿
0Stars
27Forks
12Releases

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.

0510152025302722017-012021-102026-07
Major 1Minor 1Patch 2

Each point covers 9 days.

OpenSSF Scorecard 2.6 / 10
2.6aggregate

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 19:39 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 2 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/14 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
n/aDangerous-Workflowno workflows found
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
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 24
RegistryPackageVersion constraintManifest
npmchalk1.1.1package.json
npmfancy-log1.3.0package.json
npmfstream-npm^1.2.1package.json
npmgift0.9.0package.json
npmglob7.0.3package.json
npmgulp-bump1.0.0package.json
npmgulp-filter3.0.1package.json
npmgulp-git2.3.2package.json
npmgulp-sourcemaps1.6.0package.json
npmgulp-tag-versiongithub:ikari-pl/gulp-tag-versionpackage.json
npmgulp-util3.0.7package.json
npmlodash.difference4.3.0package.json
npmlodash.merge3.3.2package.json
npmnf-conventional-changelog1.0.0package.json
npmnpm^6.8.0package.json
npmobject-values1.0.0package.json
npmpaqman1.0.0package.json
npmreadable-stream2.1.4package.json
npmrimraf2.5.4package.json
npmsemver5.0.3package.json
npmundertaker1.1.0package.json
npmvinyl-fs2.4.3package.json
npmwrap-promise1.0.1package.json
npmyargs10.0.3package.json
All dependencies 34

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

RegistryPackageVersionRelation
npmchalk1.1.1direct
npmfancy-log1.3.0direct
npmfstream-npm^1.2.1direct
npmgift0.9.0direct
npmglob7.0.3direct
npmgulp-bump1.0.0direct
npmgulp-filter3.0.1direct
npmgulp-git2.3.2direct
npmgulp-sourcemaps1.6.0direct
npmgulp-util3.0.7direct
npmlodash.difference4.3.0direct
npmlodash.merge3.3.2direct
npmnf-conventional-changelog1.0.0direct
npmnpm^6.8.0direct
npmobject-values1.0.0direct
npmpaqman1.0.0direct
npmreadable-stream2.1.4direct
npmrimraf2.5.4direct
npmsemver5.0.3direct
npmundertaker1.1.0direct
npmvinyl-fs2.4.3direct
npmwrap-promise1.0.1direct
npmyargs10.0.3direct
npmbabel-eslint6.1.2indirect
npmesdoc0.4.8indirect
npmesdoc-es7-plugin0.0.3indirect
npmeslint3.1.1indirect
npmeslint-config-netflix1.0.0-alpha.2indirect
npmistanbul0.4.5indirect
npmjscs3.0.7indirect
npmnpm-check^5.9.0indirect
npmopn-cli3.1.0indirect
npmtap-difflet^0.7.1indirect
npmtape^4.10.1indirect
Dependency advisories 9

Installing npm:unleash@2.0.2 pulls in 771 packages, direct and transitive: 9 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
semver5.0.3directhigh17.5.2
braces1.8.5indirecthigh13.0.3
cross-spawn5.1.0indirecthigh17.0.5
lodash.template3.6.2indirecthigh14.17.21
trim-newlines1.0.0indirecthigh14.0.1
dot-object1.9.0indirectmoderate12.1.3
mem1.1.0indirectmoderate14.0.0
micromatch2.3.11indirectmoderate14.0.8
yargs-parser8.1.0indirectmoderate118.1.1

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.