Public recordModerate
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-15 13:03 UTC
75lb / renamer
Rename files in bulk.
75lb/renamer holds a health index of 54 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (75/100) and lowest on Vitality (25/100). It was last updated 93 days ago. A single contributor accounts for most of its recent work.
54
overall / 100Software 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.
54
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)
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 53 is calibrated to 54 on the published index scale (record calibration 2026-08-02).
Ownership
Lloyd BrookesPersonal account
195 followers99 public repossince Dec 201175lb Software Ltd
This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.
Package ecosystems
| Registry | Package | Version | Downloads / mo | Versions | Last publish | Tags |
|---|---|---|---|---|---|---|
| npm | renamer | 5.0.3 | 139,816 | 64 | 117 days ago | renamemovemvfilefilesbulkbatch |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
25
Development activity
18Critical
How it's scored
| 9.9/36 | Push recency — last push 93 days ago |
| 1.4/36 | Commit cadence — 2/52 weeks with commits |
| 6.3/18 | Commit volume — 4 commits in the last year |
| 0/10 | OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
Inputs used
| commits_last_year | 4 |
| human_commit_share | — |
| days_since_last_push | 93 |
| active_weeks_last_year | 2 |
Release discipline
36Weak
How it's scored
| 27/27 | Ships releases — 6 releases published |
| 0/36 | Release recency — latest release 892 days ago |
| 5.4/27 | Release cadence — a release every ~405.3 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
Inputs used
| releases_count | 6 |
| latest_release_tag | v5.0.0 |
| releases_from_tags | no |
| days_since_latest_release | 892 |
| mean_days_between_releases | 405.3 |
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?
75
Popularity & adoption
59Moderate
How it's scored
| 44.5/60 | Stars — 557 stars |
| 12.2/25 | Forks — 30 forks |
| 2.7/15 | Watchers — 4 watchers |
Inputs used
| forks | 30 |
| stars | 557 |
| watchers | 4 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
85Excellent
How it's scored
| 22.5/22.5 | README |
| 22.5/22.5 | License — recognized license (MIT) |
| 18/18 | CONTRIBUTING guide |
| 13.5/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 0/6.3 | PR template |
Inputs used
| has_readme | yes |
| has_license | yes |
| readme_badges | — |
| has_contributing | yes |
| has_issue_template | no |
| has_code_of_conduct | yes |
| readme_badge_services | — |
| has_pull_request_template | no |
Ecosystem adoption (downloads)
86Excellent
How it's scored
| 68.6/80 | Monthly downloads — 139,816 downloads/month across npm |
| 0/20 | Registry dependents — not reported by this ecosystem |
Inputs used
| packages | renamer |
| dependents | — |
| ecosystems | npm |
| total_downloads | — |
| monthly_downloads | 139,816 |
| 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?
60
Maintainer resilience (bus factor)
25At Risk
How it's scored
| 9/54 | Bus factor — 1 contributor(s) cover half of all commits |
| 0.2/22.5 | Commit distribution — top contributor authored 99% of commits |
| 5.4/13.5 | Contributor breadth — 4 contributors |
| 10/10 | OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations |
Inputs used
| bus_factor | 1 |
| contributors_sampled | 4 |
| top_contributor_share | 0.989 |
How it's scored
| 39.7/42 | Issue resolution — 94% of issues closed |
| 17.1/30 | PR acceptance — 4/7 decided PRs merged |
| 0/13 | Newcomer PR acceptance — no first-time contributor's PR decided in 30d |
| 0/15 | OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0 |
Inputs used
| merged_prs | 4 |
| open_issues | 3 |
| closed_issues | 52 |
| prs_merged_7d | — |
| prs_decided_7d | — |
| prs_merged_30d | — |
| prs_decided_30d | — |
| issue_closed_ratio | 0.945 |
| closed_unmerged_prs | 3 |
| first_time_authors_30d | — |
| first_time_prs_merged_30d | — |
| first_time_prs_decided_30d | — |
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
Ownership & stewardship
64Moderate
How it's scored
| 10/30 | Ownership backing — personal (user) account |
| 0/20 | Verified domain — not applicable to user accounts |
| 16.5/25 | Owner reach — 195 followers of 75lb |
| 25/25 | Track record — 99 public repos, account ~14 yr old |
Inputs used
| followers | 195 |
| owner_type | User |
| is_verified | — |
| owner_login | 75lb |
| public_repos | 99 |
| account_age_days | 5,333 |
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
Package maintenance
100Exceptional
How it's scored
| 25/25 | Published & resolvable — 1 package(s) on npm |
| 35/35 | Publish recency — latest publish 117 days ago |
| 20/20 | Version history — 64 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
Inputs used
| packages | renamer |
| ecosystems | npm |
| any_deprecated | no |
| min_days_since_publish | 117 |
Engineering Quality
Are baseline engineering and documentation practices in place?
70
Engineering practices
60Moderate
How it's scored
| 24/24 | CI workflows — 1 workflow(s) |
| 24/24 | Tests present |
| 0/16 | Linter config |
| 0/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 0/20 | OpenSSF Scorecard: CI-Tests — no data |
Inputs used
| has_ci | yes |
| has_tests | yes |
| has_editorconfig | no |
| has_linter_config | no |
| has_precommit_config | no |
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
Documentation
85Excellent
How it's scored
| 30/30 | README |
| 25/25 | Documentation directory |
| 0/15 | Documentation / homepage site |
| 10/10 | Repository description |
| 10/10 | Topics — 15 topics |
| 10/10 | Wiki |
Inputs used
| topics | renamer, rename-files, regular-expression, javascript, glob-pattern, nodejs, rename, filesystem, cross-platform, move, file, batch, command-line-tool, command-line-app, javascript-library |
| has_wiki | yes |
| homepage | — |
| docs_site | — |
| has_readme | yes |
| has_docs_dir | yes |
| has_description | yes |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
38
Security posture
38Weak
How it's scored
| 7.5/7.5 | Binary-Artifacts — no binaries found in the repo |
| 0/7.5 | Branch-Protection — branch protection not enabled on development/release branches |
| 0/2.5 | CI-Tests — no data |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 0/7.5 | Code-Review — Found 0/30 approved changesets -- score normalized to 0 |
| 2.5/2.5 | Contributors — project has 4 contributing companies or organizations |
| 10/10 | Dangerous-Workflow — no dangerous workflow patterns detected |
| 0/7.5 | Dependency-Update-Tool — no update tool detected |
| 0/5 | Fuzzing — project is not fuzzed |
| 2.5/2.5 | License — license file detected |
| 0/7.5 | Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| 0/5 | Packaging — no data |
| 0/5 | Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0 |
| 0/5 | SAST — no SAST tool detected |
| 0/5 | Security-Policy — security policy file not detected |
| 0/7.5 | Signed-Releases — no data |
| 6.8/7.5 | Token-Permissions — detected GitHub workflow tokens with excessive permissions |
| 4.5/7.5 | Vulnerabilities — 4 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 15 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 3 |
| scorecard_aggregate | 3.8 |
Excluded from scoring (no data or not applicable): CI-Tests, Packaging, Signed-Releases. Remaining weights renormalized.
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.
39
Agent context & guidance
1Critical
How it's scored
| 0/45 | Agent instructions — no CLAUDE.md / AGENTS.md / editor rules |
| 0/15 | Machine-readable docs (llms.txt) |
| 0/40 | Legible commit history — no data |
Inputs used
| has_llms_txt | no |
| llms_txt_url | — |
| legible_history_share | — |
| agent_instruction_files | — |
| agent_instruction_max_bytes | — |
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
| 0/18 | One-command bootstrap |
| 22/22 | Automated tests |
| 0/11 | Lint / format config |
| 0/11 | Static type checking |
| 10/10 | Reproducible environment — lockfile |
| 0/10 | Demonstrated agent practice — no data |
| 0/8 | Automated maintenance — no data |
| 0/10 | OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0 |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | package-lock.json |
| has_dockerfile | no |
| typed_language | no |
| bootstrap_files | — |
| has_devcontainer | no |
| has_linter_config | no |
| typecheck_configs | — |
| agent_commit_share | — |
| toolchain_manifests | — |
| dependency_bot_commit_share | — |
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
Code legibility for models
55Moderate
How it's scored
| 0/45 | Type-checkable code — JavaScript without a type-check config |
| 55/55 | Manageable file sizes — 0/36 source files over 60KB |
Inputs used
| primary_language | JavaScript |
| largest_source_bytes | 11,536 |
| source_files_sampled | 36 |
| oversized_source_files | 0 |
Machine-readable interfaces
100Exceptional
How it's scored
| 0/40 | API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software |
| 0/20 | MCP server — not applicable to this kind of software |
| 40/40 | Runnable examples — example |
Inputs used
| example_dirs | example |
| has_mcp_signal | no |
| api_schema_files | — |
| interfaces_expected_of | — |
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.
Key facts
557GitHub stars
4contributors
4commits, last 12 months
93days since last push
6releases
1bus factor
3open issues
npmpackage ecosystems
More detail
OpenSSF Scorecard 3.8 / 10
3.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).
| 10 | Binary-Artifacts | no binaries found in the repo |
| 0 | Branch-Protection | branch protection not enabled on development/release branches |
| n/a | CI-Tests | no pull request found |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 0 | Code-Review | Found 0/30 approved changesets -- score normalized to 0 |
| 10 | Contributors | project has 4 contributing companies or organizations |
| 10 | Dangerous-Workflow | no dangerous workflow patterns detected |
| 0 | Dependency-Update-Tool | no update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 10 | License | license file detected |
| 0 | Maintained | 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| n/a | Packaging | packaging workflow not detected |
| 0 | Pinned-Dependencies | dependency not pinned by hash detected -- score normalized to 0 |
| 0 | SAST | no SAST tool detected |
| 0 | Security-Policy | security policy file not detected |
| n/a | Signed-Releases | no releases found |
| 9 | Token-Permissions | detected GitHub workflow tokens with excessive permissions |
| 6 | Vulnerabilities | 4 existing vulnerabilities detected |
Direct dependencies 12
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| npm | array-back | ^6.2.3 | package.json |
| npm | chalk | ^5.6.2 | package.json |
| npm | command-line-args | ^6.0.1 | package.json |
| npm | command-line-usage | ^7.0.4 | package.json |
| npm | current-module-paths | ^1.1.3 | package.json |
| npm | fast-diff | ^1.3.0 | package.json |
| npm | file-set | ^5.3.0 | package.json |
| npm | global-directory | ^4.0.1 | package.json |
| npm | load-module | ^5.0.0 | package.json |
| npm | printj | ^1.3.1 | package.json |
| npm | stream-read-all | ^5.0.2 | package.json |
| npm | typical | ^7.3.0 | package.json |
All dependencies 45
Full resolved dependency set from the GitHub dependency graph: 13 direct and 32 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.
| Registry | Package | Version | Relation |
|---|---|---|---|
| npm | array-back | 6.2.3 | direct |
| npm | chalk | 4.1.2 | direct |
| npm | chalk | 5.6.2 | direct |
| npm | command-line-args | 6.0.1 | direct |
| npm | command-line-usage | 7.0.4 | direct |
| npm | current-module-paths | 1.1.3 | direct |
| npm | fast-diff | 1.3.0 | direct |
| npm | file-set | 5.3.0 | direct |
| npm | global-directory | 4.0.1 | direct |
| npm | load-module | 5.0.0 | direct |
| npm | printj | 1.3.1 | direct |
| npm | stream-read-all | 5.0.2 | direct |
| npm | typical | 7.3.0 | direct |
| npm | @nodelib/fs.scandir | 2.1.5 | indirect |
| npm | @nodelib/fs.stat | 2.0.5 | indirect |
| npm | @nodelib/fs.walk | 1.2.8 | indirect |
| npm | ansi-styles | 4.3.0 | indirect |
| npm | braces | 3.0.3 | indirect |
| npm | chalk-template | 0.4.0 | indirect |
| npm | color-convert | 2.0.1 | indirect |
| npm | color-name | 1.1.4 | indirect |
| npm | fast-glob | 3.3.2 | indirect |
| npm | fastq | 1.17.1 | indirect |
| npm | fill-range | 7.1.1 | indirect |
| npm | find-replace | 5.0.2 | indirect |
| npm | glob-parent | 5.1.2 | indirect |
| npm | has-flag | 4.0.0 | indirect |
| npm | ini | 4.1.1 | indirect |
| npm | is-extglob | 2.1.1 | indirect |
| npm | is-glob | 4.0.3 | indirect |
| npm | is-number | 7.0.0 | indirect |
| npm | lodash | 4.17.21 | indirect |
| npm | lodash.camelcase | 4.3.0 | indirect |
| npm | merge2 | 1.4.1 | indirect |
| npm | micromatch | 4.0.8 | indirect |
| npm | mkdirp2 | 1.0.5 | indirect |
| npm | picomatch | 2.3.1 | indirect |
| npm | queue-microtask | 1.2.3 | indirect |
| npm | renamer-case | 2.0.2 | indirect |
| npm | reusify | 1.0.4 | indirect |
| npm | run-parallel | 1.2.0 | indirect |
| npm | supports-color | 7.2.0 | indirect |
| npm | table-layout | 4.1.1 | indirect |
| npm | to-regex-range | 5.0.1 | indirect |
| npm | wordwrapjs | 5.1.0 | indirect |
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.
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.11.0 — full methodology · metrics wiki.
How one result sits in the wider record: aggregate statistics — npm.