Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-14 02:43 UTC

enszrlu / NextStep

Lightweight onboarding library for Next.js

TypeScriptMIT★ 1,037 stars⑂ 43 forkssince Sep 2024View on GitHub ↗

enszrlu/NextStep holds a health index of 45 out of 100, placing it in the Weak band. It scores highest on Community & Adoption (66/100) and lowest on Engineering Quality (27/100). It was last updated 55 days ago. A single contributor accounts for most of its recent work.

45
overall / 100
Weak

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.

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

Ownership

Alex Enes ZorluPersonal account
17 followers50 public repossince May 2020

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?

52Moderate · 21% of overall
How it's scored
18/36Push recencylast push 55 days ago
2.1/36Commit cadence3/52 weeks with commits
9.7/18Commit volume11 commits in the last year
2/10OpenSSF Scorecard: Maintained1 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 2
Inputs used
commits_last_year11
human_commit_share1
days_since_last_push55
active_weeks_last_year3
How it's scored
27/27Ships releases23 releases published
36/36Release recencylatest release 55 days ago
19.8/27Release cadencea release every ~69.8 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count23
latest_release_tagv2.3.1-beta.0
releases_from_tagsno
days_since_latest_release55
mean_days_between_releases69.8

Community & Adoption

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

66Good · 17% of overall
How it's scored
48.9/60Stars1,037 stars
13.5/25Forks43 forks
3.3/15Watchers5 watchers
Inputs used
forks43
stars1,037
watchers5
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
71.3/80Monthly downloads223,289 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesnextstepjs
dependents
ecosystemsnpm
total_downloads
monthly_downloads223,289
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?

55Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
2/22.5Commit distributiontop contributor authored 91% of commits
4.1/13.5Contributor breadth3 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.911
How it's scored
39.7/42Issue resolution94% of issues closed
16.8/30PR acceptance14/25 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 1/13 approved changesets -- score normalized to 0
Inputs used
merged_prs14
open_issues3
closed_issues52
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.945
closed_unmerged_prs11
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
9/25Owner reach17 followers of enszrlu
24.4/25Track record50 public repos, account ~6 yr old
Inputs used
followers17
owner_typeUser
is_verified
owner_loginenszrlu
public_repos50
account_age_days2,304
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 55 days ago
20/20Version history41 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesnextstepjs
ecosystemsnpm
any_deprecatedno
min_days_since_publish55

Engineering Quality

Are baseline engineering and documentation practices in place?

27At Risk · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 8 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://nextstepjs.com
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepagehttps://nextstepjs.com
docs_sitehttps://nextstepjs.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

33At Risk · 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
0/2.5CI-Tests0 out of 8 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/7.5Code-ReviewFound 1/13 approved changesets -- score normalized to 0
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
1.5/7.5Maintained1 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 2
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsno data
0/7.5Vulnerabilities45 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate1.6
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Token-Permissions. 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
advisories54
affected_packages9
assessed_packages52
unassessed_packages0
affected_by_severitycritical 1, high 8
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 52 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.

33At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
11.7/40Legible commit history22 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.22
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
11/11Static type checkingtsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsno
lockfilespnpm-lock.yaml
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
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
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/14 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes49,064
source_files_sampled14
oversized_source_files0

Key facts

1,037GitHub stars
3contributors
11commits, last 12 months
55days since last push
23releases
1bus factor
3open 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 ★ / 43 ⇿
0Stars
43Forks
18Releases

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.

010203040504332024-092025-092026-08
Major 0Minor 1Patch 0

Each point covers 2 days.

OpenSSF Scorecard 1.6 / 10
1.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-14 02:43 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 8 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/13 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
2Maintained1 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 2
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
0Signed-ReleasesProject has not signed or included provenance with any releases.
n/aToken-PermissionsNo tokens found
0Vulnerabilities45 existing vulnerabilities detected
All dependencies 52

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

RegistryPackageVersionRelation
npm@next/env14.2.35indirect
npm@next/swc-darwin-arm6414.2.33indirect
npm@next/swc-darwin-x6414.2.33indirect
npm@next/swc-linux-arm64-gnu14.2.33indirect
npm@next/swc-linux-arm64-musl14.2.33indirect
npm@next/swc-linux-x64-gnu14.2.33indirect
npm@next/swc-linux-x64-musl14.2.33indirect
npm@next/swc-win32-arm64-msvc14.2.33indirect
npm@next/swc-win32-ia32-msvc14.2.33indirect
npm@next/swc-win32-x64-msvc14.2.33indirect
npm@remix-run/react2.17.2indirect
npm@remix-run/router1.23.0indirect
npm@remix-run/server-runtime2.17.2indirect
npm@swc/counter0.1.3indirect
npm@swc/helpers0.5.5indirect
npm@types/cookie0.6.0indirect
npm@types/history4.7.11indirect
npm@types/prop-types15.7.15indirect
npm@types/react18.3.27indirect
npm@types/react-dom18.3.7indirect
npm@types/react-router5.1.20indirect
npm@web3-storage/multipart-parser1.0.0indirect
npmbusboy1.6.0indirect
npmcaniuse-lite1.0.30001762indirect
npmclient-only0.0.1indirect
npmcookie0.7.2indirect
npmcookie1.1.1indirect
npmcsstype3.2.3indirect
npmframer-motion12.23.26indirect
npmgraceful-fs4.2.11indirect
npmmotion12.23.26indirect
npmmotion-dom12.23.23indirect
npmmotion-utils12.23.6indirect
npmnanoid3.3.11indirect
npmnext14.2.35indirect
npmpicocolors1.1.1indirect
npmpostcss8.4.31indirect
npmreact19.2.3indirect
npmreact-compiler-runtime19.0.0-beta-201e55d-20241215indirect
npmreact-dom19.2.3indirect
npmreact-router6.30.0indirect
npmreact-router7.11.0indirect
npmreact-router-dom6.30.0indirect
npmscheduler0.27.0indirect
npmset-cookie-parser2.7.2indirect
npmsource-map0.7.6indirect
npmsource-map-js1.2.1indirect
npmstreamsearch1.1.0indirect
npmstyled-jsx5.1.1indirect
npmtslib2.8.1indirect
npmturbo-stream2.4.1indirect
npmtypescript5.9.3indirect
Dependency advisories 9

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

PackageVersionRelationSeverityAdvisoriesFixed in
next14.2.35indirectcritical2316.3.3
@remix-run/react2.17.2indirecthigh17.12.0
@remix-run/router1.23.0indirecthigh27.14.1
@remix-run/server-runtime2.17.2indirecthigh27.15.0
nanoid3.3.11indirecthigh35.1.16
postcss8.4.31indirecthigh48.5.23
react-router6.30.0indirecthigh47.18.0
react-router7.11.0indirecthigh147.18.0
turbo-stream2.4.1indirecthigh17.14.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.