Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-09 23:48 UTC

bramus / js-pagination-sequence

Generate a sequence of numbers for use in a pagination system, the clever way.

JavaScriptMIT★ 141 stars⑂ 4 forkssince Dec 2021View on GitHub ↗

bramus/js-pagination-sequence holds a health index of 35 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (59/100) and lowest on Vitality (20/100). It was last updated 1149 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

BramusPersonal account
916 followers143 public repossince Mar 2010Google

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
npm@bramus/pagination-sequence1.2.15,469111149 days agopaginationsequence

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,149 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,149
active_weeks_last_year0
How it's scored
16.2/27Ships releases — 7 version tags (no GitHub releases)
0/36Release recency — latest release 1,727 days ago
27/27Release cadence — a release every ~2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count7
latest_release_tagv1.1.2
releases_from_tagsyes
days_since_latest_release1,727
mean_days_between_releases2
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?

49Weak · 17% of overall
How it's scored
34.8/60Stars — 141 stars
4/25Forks — 4 forks
1.7/15Watchers — 3 watchers
Inputs used
forks4
stars141
watchers3
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
49.8/80Monthly downloads — 5,469 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@bramus/pagination-sequence
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads5,469
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?

59Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.7/22.5Commit distribution — top contributor authored 97% of commits
2.7/13.5Contributor breadth — 2 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.969
How it's scored
42/42Issue resolution — 100% of issues closed
30/30PR acceptance — 1/1 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 1/30 approved changesets -- score normalized to 0
Inputs used
merged_prs1
open_issues0
closed_issues6
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
21.3/25Owner reach — 916 followers of bramus
25/25Track record — 143 public repos, account ~16 yr old
Inputs used
followers916
owner_typeUser
is_verified—
owner_loginbramus
public_repos143
account_age_days6,036
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable — 1 package(s) on npm
4/35Publish recency — latest publish 1,149 days ago
20/20Version history — 11 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@bramus/pagination-sequence
ecosystemsnpm
any_deprecatedno
min_days_since_publish1,149

Engineering Quality

Are baseline engineering and documentation practices in place?

38Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 1 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigyes
has_linter_configno
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?

34At 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 1 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/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
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
0/7.5Vulnerabilities — 27 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate1.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
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_packages1
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:@bramus/pagination-sequence@1.2.1 runtime dependency closure — what installing the published package pulls in — 1 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.

31At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
11.7/40Legible commit history — 7 of 32 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.219
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 32
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
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/2 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes6,868
source_files_sampled2
oversized_source_files0

Key facts

141GitHub stars
2contributors
0commits, last 12 months
1,149days since last push
7releases
1bus factor
0open 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 ★ / 4 ⇿
0Stars
4Forks
6Releases

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.

223344422021-122024-022026-04
Major 0Minor 1Patch 5

Each point covers 5 days.

OpenSSF Scorecard 1.8 / 10
1.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-09 23:48 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 1 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/30 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
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
0Vulnerabilities27 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
npm@bramus/range^1.1.2package.json
All dependencies 99

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

RegistryPackageVersionRelation
npm@bramus/range1.1.2direct
npm@ungap/promise-all-settled1.1.2indirect
npmansi-colors4.1.1indirect
npmansi-regex5.0.1indirect
npmansi-styles4.3.0indirect
npmanymatch3.1.2indirect
npmargparse2.0.1indirect
npmbalanced-match1.0.2indirect
npmbinary-extensions2.2.0indirect
npmbrace-expansion1.1.11indirect
npmbraces3.0.2indirect
npmbrowser-stdout1.3.1indirect
npmcamelcase6.2.1indirect
npmchalk4.1.2indirect
npmchokidar3.5.2indirect
npmcliui7.0.4indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmconcat-map0.0.1indirect
npmdebug4.3.2indirect
npmdecamelize4.0.0indirect
npmdiff5.0.0indirect
npmemoji-regex8.0.0indirect
npmesbuild0.14.5indirect
npmesbuild-android-arm640.14.5indirect
npmesbuild-darwin-640.14.5indirect
npmesbuild-darwin-arm640.14.5indirect
npmesbuild-freebsd-640.14.5indirect
npmesbuild-freebsd-arm640.14.5indirect
npmesbuild-linux-320.14.5indirect
npmesbuild-linux-640.14.5indirect
npmesbuild-linux-arm0.14.5indirect
npmesbuild-linux-arm640.14.5indirect
npmesbuild-linux-mips64le0.14.5indirect
npmesbuild-linux-ppc64le0.14.5indirect
npmesbuild-netbsd-640.14.5indirect
npmesbuild-openbsd-640.14.5indirect
npmesbuild-sunos-640.14.5indirect
npmesbuild-windows-320.14.5indirect
npmesbuild-windows-640.14.5indirect
npmesbuild-windows-arm640.14.5indirect
npmescalade3.1.1indirect
npmescape-string-regexp4.0.0indirect
npmfill-range7.0.1indirect
npmfind-up5.0.0indirect
npmflat5.0.2indirect
npmfs.realpath1.0.0indirect
npmfsevents2.3.2indirect
npmget-caller-file2.0.5indirect
npmglob7.1.7indirect
npmglob-parent5.1.2indirect
npmgrowl1.10.5indirect
npmhas-flag4.0.0indirect
npmhe1.2.0indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npmis-binary-path2.1.0indirect
npmis-extglob2.1.1indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-glob4.0.3indirect
npmis-number7.0.0indirect
npmis-plain-obj2.1.0indirect
npmis-unicode-supported0.1.0indirect
npmisexe2.0.0indirect
npmjs-yaml4.1.0indirect
npmlocate-path6.0.0indirect
npmlog-symbols4.1.0indirect
npmminimatch3.0.4indirect
npmmocha9.1.3indirect
npmms2.1.2indirect
npmms2.1.3indirect
npmnanoid3.1.25indirect
npmnormalize-path3.0.0indirect
npmonce1.4.0indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmpath-exists4.0.0indirect
npmpath-is-absolute1.0.1indirect
npmpicomatch2.3.0indirect
npmrandombytes2.1.0indirect
npmreaddirp3.6.0indirect
npmrequire-directory2.1.1indirect
npmsafe-buffer5.2.1indirect
npmserialize-javascript6.0.0indirect
npmstring-width4.2.3indirect
npmstrip-ansi6.0.1indirect
npmstrip-json-comments3.1.1indirect
npmsupports-color7.2.0indirect
npmsupports-color8.1.1indirect
npmto-regex-range5.0.1indirect
npmwhich2.0.2indirect
npmworkerpool6.1.5indirect
npmwrap-ansi7.0.0indirect
npmwrappy1.0.2indirect
npmy18n5.0.8indirect
npmyargs16.2.0indirect
npmyargs-parser20.2.4indirect
npmyargs-unparser2.0.0indirect
npmyocto-queue0.1.0indirect
Dependency advisories 0

Installing npm:@bramus/pagination-sequence@1.2.1 pulls in 1 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.