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

progfay / nextjs-ssg-rewrite-rule-gen

Generate nginx rewrite rules for Next.js SSG (Pages Router)

TypeScriptMIT★ 13 stars⑂ 1 forksince Jan 2024View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

progfay/nextjs-ssg-rewrite-rule-gen holds a health index of 50 out of 100, placing it in the Moderate band. It scores highest on AI Readiness (67/100) and lowest on Community & Adoption (39/100). It was last updated 3 days ago. A single contributor accounts for most of its recent work.

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

50
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

Shunsuke ManoPersonal account
139 followers172 public repossince May 2016@recruit-tech

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 publish
npm@progfay/nextjs-ssg-rewrite-rule-gen1.3.12,611555 days ago

Metrics by category

Vitality

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

52Moderate · 21% of overall
How it's scored
36/36Push recency — last push 3 days ago
22.2/36Commit cadence — 32/52 weeks with commits
18/18Commit volume — 105 commits in the last year
10/10OpenSSF Scorecard: Maintained — 13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year105
human_commit_share0.56
days_since_last_push3
active_weeks_last_year32
How it's scored
0/27Ships releases — no releases published
0/36Release recency — no releases
0/27Release cadence — no releases
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count0
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?

39Weak · 17% of overall
How it's scored
17.5/60Stars — 13 stars
0/25Forks — 1 forks
0/15Watchers — 1 watchers
Inputs used
forks1
stars13
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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
45.6/80Monthly downloads — 2,611 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@progfay/nextjs-ssg-rewrite-rule-gen
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads2,611
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 factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
21/42Issue resolution — 50% of issues closed
29.2/30PR acceptance — 140/144 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/5 approved changesets -- score normalized to 0
Inputs used
merged_prs140
open_issues1
closed_issues1
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.5
closed_unmerged_prs4
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 backing — personal (user) account
0/20Verified domain — not applicable to user accounts
15.4/25Owner reach — 139 followers of progfay
25/25Track record — 172 public repos, account ~10 yr old
Inputs used
followers139
owner_typeUser
is_verified—
owner_loginprogfay
public_repos172
account_age_days3,764
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 55 days ago
20/20Version history — 5 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@progfay/nextjs-ssg-rewrite-rule-gen
ecosystemsnpm
any_deprecatedno
min_days_since_publish55

Engineering Quality

Are baseline engineering and documentation practices in place?

40Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 13 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://npmjs.com/package/@progfay/nextjs-ssg-rewrite-rule-gen
10/10Repository description
10/10Topics — 6 topics
0/10Wiki
Inputs used
topicsnextjs, nginx, pages-router, rewrite-rules, ssg, static-export
has_wikino
homepagehttps://npmjs.com/package/@progfay/nextjs-ssg-rewrite-rule-gen
docs_sitehttps://npmjs.com/package/@progfay/nextjs-ssg-rewrite-rule-gen
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

58Moderate · 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 13 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 0/5 approved changesets -- score normalized to 0
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
0/10Dangerous-Workflow — no data
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
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
6.8/7.5Vulnerabilities — 1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate4.8
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories2
affected_packages2
assessed_packages162
unassessed_packages0
affected_by_severitymoderate 2
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 162 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.

67Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://nextjs.org/llms.txt)
40/40Legible commit history — 49 of 56 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://nextjs.org/llms.txt
legible_history_share0.875
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — tsconfig.json
10/10Reproducible environment — lockfile
6/10Demonstrated agent practice — 3 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 44 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share0.03
toolchain_manifests—
dependency_bot_commit_share0.44
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/23 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes4,843
source_files_sampled23
oversized_source_files0

Key facts

13GitHub stars
1contributors
105commits, last 12 months
3days since last push
0releases
1bus factor
1open issues
npmpackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 4.8 / 10
4.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-09-14 13:13 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/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
0Code-ReviewFound 0/5 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained13 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
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
9Vulnerabilities1 existing vulnerabilities detected
All dependencies 162

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

RegistryPackageVersionRelation
npm@babel/code-frame7.29.0indirect
npm@babel/helper-validator-identifier7.28.5indirect
npm@babel/runtime7.29.7indirect
npm@blazediff/core1.9.1indirect
npm@jridgewell/sourcemap-codec1.5.5indirect
npm@oxc-project/runtime0.139.0indirect
npm@oxc-project/types0.139.0indirect
npm@oxfmt/binding-android-arm-eabi0.58.0indirect
npm@oxfmt/binding-android-arm640.58.0indirect
npm@oxfmt/binding-darwin-arm640.58.0indirect
npm@oxfmt/binding-darwin-x640.58.0indirect
npm@oxfmt/binding-freebsd-x640.58.0indirect
npm@oxfmt/binding-linux-arm-gnueabihf0.58.0indirect
npm@oxfmt/binding-linux-arm-musleabihf0.58.0indirect
npm@oxfmt/binding-linux-arm64-gnu0.58.0indirect
npm@oxfmt/binding-linux-arm64-musl0.58.0indirect
npm@oxfmt/binding-linux-ppc64-gnu0.58.0indirect
npm@oxfmt/binding-linux-riscv64-gnu0.58.0indirect
npm@oxfmt/binding-linux-riscv64-musl0.58.0indirect
npm@oxfmt/binding-linux-s390x-gnu0.58.0indirect
npm@oxfmt/binding-linux-x64-gnu0.58.0indirect
npm@oxfmt/binding-linux-x64-musl0.58.0indirect
npm@oxfmt/binding-openharmony-arm640.58.0indirect
npm@oxfmt/binding-win32-arm64-msvc0.58.0indirect
npm@oxfmt/binding-win32-ia32-msvc0.58.0indirect
npm@oxfmt/binding-win32-x64-msvc0.58.0indirect
npm@oxlint-tsgolint/darwin-arm640.24.0indirect
npm@oxlint-tsgolint/darwin-x640.24.0indirect
npm@oxlint-tsgolint/linux-arm640.24.0indirect
npm@oxlint-tsgolint/linux-x640.24.0indirect
npm@oxlint-tsgolint/win32-arm640.24.0indirect
npm@oxlint-tsgolint/win32-x640.24.0indirect
npm@oxlint/binding-android-arm-eabi1.73.0indirect
npm@oxlint/binding-android-arm641.73.0indirect
npm@oxlint/binding-darwin-arm641.73.0indirect
npm@oxlint/binding-darwin-x641.73.0indirect
npm@oxlint/binding-freebsd-x641.73.0indirect
npm@oxlint/binding-linux-arm-gnueabihf1.73.0indirect
npm@oxlint/binding-linux-arm-musleabihf1.73.0indirect
npm@oxlint/binding-linux-arm64-gnu1.73.0indirect
npm@oxlint/binding-linux-arm64-musl1.73.0indirect
npm@oxlint/binding-linux-ppc64-gnu1.73.0indirect
npm@oxlint/binding-linux-riscv64-gnu1.73.0indirect
npm@oxlint/binding-linux-riscv64-musl1.73.0indirect
npm@oxlint/binding-linux-s390x-gnu1.73.0indirect
npm@oxlint/binding-linux-x64-gnu1.73.0indirect
npm@oxlint/binding-linux-x64-musl1.73.0indirect
npm@oxlint/binding-openharmony-arm641.73.0indirect
npm@oxlint/binding-win32-arm64-msvc1.73.0indirect
npm@oxlint/binding-win32-ia32-msvc1.73.0indirect
npm@oxlint/binding-win32-x64-msvc1.73.0indirect
npm@oxlint/plugins1.73.0indirect
npm@polka/url1.0.0-next.29indirect
npm@standard-schema/spec1.1.0indirect
npm@testing-library/dom10.4.1indirect
npm@testing-library/user-event14.6.1indirect
npm@types/aria-query5.0.4indirect
npm@types/chai5.2.3indirect
npm@types/deep-eql4.0.2indirect
npm@types/estree1.0.9indirect
npm@types/node24.13.3indirect
npm@vitest/browser4.1.10indirect
npm@vitest/browser-preview4.1.10indirect
npm@vitest/expect4.1.10indirect
npm@vitest/mocker4.1.10indirect
npm@vitest/pretty-format4.1.10indirect
npm@vitest/runner4.1.10indirect
npm@vitest/snapshot4.1.10indirect
npm@vitest/spy4.1.10indirect
npm@vitest/utils4.1.10indirect
npm@voidzero-dev/vite-plus-core0.2.5indirect
npm@voidzero-dev/vite-plus-darwin-arm640.2.5indirect
npm@voidzero-dev/vite-plus-darwin-x640.2.5indirect
npm@voidzero-dev/vite-plus-linux-arm64-gnu0.2.5indirect
npm@voidzero-dev/vite-plus-linux-arm64-musl0.2.5indirect
npm@voidzero-dev/vite-plus-linux-x64-gnu0.2.5indirect
npm@voidzero-dev/vite-plus-linux-x64-musl0.2.5indirect
npm@voidzero-dev/vite-plus-win32-arm64-msvc0.2.5indirect
npm@voidzero-dev/vite-plus-win32-x64-msvc0.2.5indirect
npm@yuku-codegen/binding-darwin-arm640.5.48indirect
npm@yuku-codegen/binding-darwin-x640.5.48indirect
npm@yuku-codegen/binding-freebsd-x640.5.48indirect
npm@yuku-codegen/binding-linux-arm-gnu0.5.48indirect
npm@yuku-codegen/binding-linux-arm-musl0.5.48indirect
npm@yuku-codegen/binding-linux-arm64-gnu0.5.48indirect
npm@yuku-codegen/binding-linux-arm64-musl0.5.48indirect
npm@yuku-codegen/binding-linux-x64-gnu0.5.48indirect
npm@yuku-codegen/binding-linux-x64-musl0.5.48indirect
npm@yuku-codegen/binding-win32-arm640.5.48indirect
npm@yuku-codegen/binding-win32-x640.5.48indirect
npm@yuku-parser/binding-darwin-arm640.5.48indirect
npm@yuku-parser/binding-darwin-x640.5.48indirect
npm@yuku-parser/binding-freebsd-x640.5.48indirect
npm@yuku-parser/binding-linux-arm-gnu0.5.48indirect
npm@yuku-parser/binding-linux-arm-musl0.5.48indirect
npm@yuku-parser/binding-linux-arm64-gnu0.5.48indirect
npm@yuku-parser/binding-linux-arm64-musl0.5.48indirect
npm@yuku-parser/binding-linux-x64-gnu0.5.48indirect
npm@yuku-parser/binding-linux-x64-musl0.5.48indirect
npm@yuku-parser/binding-win32-arm640.5.48indirect
npm@yuku-parser/binding-win32-x640.5.48indirect
npm@yuku-toolchain/types0.5.43indirect
npmansi-regex5.0.1indirect
npmansi-styles5.2.0indirect
npmaria-query5.3.0indirect
npmassertion-error2.0.1indirect
npmchai6.2.2indirect
npmconvert-source-map2.0.0indirect
npmdequal2.0.3indirect
npmdetect-libc2.1.2indirect
npmdom-accessibility-api0.5.16indirect
npmes-module-lexer2.3.1indirect
npmestree-walker3.0.3indirect
npmexpect-type1.4.0indirect
npmfdir6.5.0indirect
npmfsevents2.3.3indirect
npmjs-tokens4.0.0indirect
npmlightningcss1.33.0indirect
npmlightningcss-android-arm641.33.0indirect
npmlightningcss-darwin-arm641.33.0indirect
npmlightningcss-darwin-x641.33.0indirect
npmlightningcss-freebsd-x641.33.0indirect
npmlightningcss-linux-arm-gnueabihf1.33.0indirect
npmlightningcss-linux-arm64-gnu1.33.0indirect
npmlightningcss-linux-arm64-musl1.33.0indirect
npmlightningcss-linux-x64-gnu1.33.0indirect
npmlightningcss-linux-x64-musl1.33.0indirect
npmlightningcss-win32-arm64-msvc1.33.0indirect
npmlightningcss-win32-x64-msvc1.33.0indirect
npmlz-string1.5.0indirect
npmmagic-string0.30.21indirect
npmmrmime2.0.1indirect
npmnanoid3.3.18indirect
npmobug2.1.4indirect
npmoxfmt0.58.0indirect
npmoxlint1.73.0indirect
npmoxlint-tsgolint0.24.0indirect
npmpathe2.0.3indirect
npmpicocolors1.1.1indirect
npmpicomatch4.0.4indirect
npmpngjs7.0.0indirect
npmpostcss8.5.26indirect
npmpretty-format27.5.1indirect
npmreact-is17.0.2indirect
npmsiginfo2.0.0indirect
npmsirv3.0.2indirect
npmsource-map-js1.2.1indirect
npmstackback0.0.2indirect
npmstd-env4.2.0indirect
npmtinybench2.9.0indirect
npmtinyexec1.2.4indirect
npmtinyglobby0.2.17indirect
npmtinypool2.1.0indirect
npmtinyrainbow3.1.0indirect
npmtotalist3.0.1indirect
npmundici-types7.18.2indirect
npmvite-plus0.2.5indirect
npmvitest4.1.10indirect
npmwhy-is-node-running2.3.0indirect
npmws8.21.1indirect
npmyuku-codegen0.5.48indirect
npmyuku-parser0.5.48indirect
Dependency advisories 2

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

PackageVersionRelationSeverityAdvisoriesFixed in
@vitest/mocker4.1.10indirectmoderate15.0.0-rc.2
vitest4.1.10indirectmoderate15.0.0-rc.2

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.