Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-17 02:43 UTC

Meshiest / brs-js

Brickadia save file parsing library

TypeScriptMIT★ 7 stars⑂ 8 forkssince Sep 2019View on GitHub ↗

Meshiest/brs-js holds a health index of 45 out of 100, placing it in the Weak band. It scores highest on AI Readiness (68/100) and lowest on Vitality (35/100). It was last updated 8 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

IsaacPersonal account
62 followers145 public repossince Apr 2013RackN

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
npmbrs-js4.0.51,360808 days agobrsbrickadiasavefileformat

Metrics by category

Vitality

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

35Weak · 21% of overall
How it's scored
28.8/36Push recency — last push 8 days ago
7.6/36Commit cadence — 11/52 weeks with commits
13.4/18Commit volume — 30 commits in the last year
7/10OpenSSF Scorecard: Maintained — 9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
Inputs used
commits_last_year30
human_commit_share0.97
days_since_last_push8
active_weeks_last_year11
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?

38Weak · 17% of overall
How it's scored
12.6/60Stars — 7 stars
7/25Forks — 8 forks
0/15Watchers — 1 watchers
Inputs used
forks8
stars7
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
41.8/80Monthly downloads — 1,360 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesbrs-js
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads1,360
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?

58Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.2/22.5Commit distribution — top contributor authored 95% of commits
6.8/13.5Contributor breadth — 5 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled5
top_contributor_share0.948
How it's scored
42/42Issue resolution — 100% of issues closed
14.1/30PR acceptance — 8/17 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/27 approved changesets -- score normalized to 0
Inputs used
merged_prs8
open_issues0
closed_issues3
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs9
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
12.9/25Owner reach — 62 followers of Meshiest
25/25Track record — 145 public repos, account ~13 yr old
Inputs used
followers62
owner_typeUser
is_verified—
owner_loginMeshiest
public_repos145
account_age_days4,965
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 8 days ago
20/20Version history — 80 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesbrs-js
ecosystemsnpm
any_deprecatedno
min_days_since_publish8

Engineering Quality

Are baseline engineering and documentation practices in place?

44Weak · 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 1 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://www.npmjs.com/package/brs-js
10/10Repository description
10/10Topics — 4 topics
10/10Wiki
Inputs used
topicsbrickadia, decoding-library, save-files, encoding-library
has_wikiyes
homepagehttps://www.npmjs.com/package/brs-js
docs_sitehttps://www.npmjs.com/package/brs-js
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

56Moderate · 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 0/27 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
5.2/7.5Maintained — 9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
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_aggregate4.5
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:brs-js@4.0.5 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.

68Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
24.2/40Legible commit history — 44 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.454
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — justfile
22/22Automated tests
0/11Lint / format config
11/11Static type checking — test/tsconfig.json, tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 3 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_filesjustfile
has_devcontainerno
has_linter_configno
typecheck_configstest/tsconfig.json, tsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.03
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)
52.4/55Manageable file sizes — 4/86 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes372,060
source_files_sampled86
oversized_source_files4
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
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

7GitHub stars
5contributors
30commits, last 12 months
8days since last push
0releases
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 ★ / 8 ⇿
0Stars
8Forks

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.

123456612020-062022-122025-07

Each point covers 5 days.

OpenSSF Scorecard 4.5 / 10
4.5aggregate

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-11-17 02:43 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 0/27 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
7Maintained9 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 7
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 1
RegistryPackageVersion constraintManifest
npmdetect-node^2.0.4package.json
All dependencies 116

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

RegistryPackageVersionRelation
npmdetect-node2.0.4direct
npm@jridgewell/sourcemap-codec1.6.0indirect
npm@noble/hashes2.2.0indirect
npm@oxc-project/types0.155.0indirect
npm@rolldown/binding-android-arm-eabi1.2.15indirect
npm@rolldown/binding-android-arm641.2.15indirect
npm@rolldown/binding-darwin-arm641.2.15indirect
npm@rolldown/binding-darwin-x641.2.15indirect
npm@rolldown/binding-freebsd-x641.2.15indirect
npm@rolldown/binding-linux-arm-gnueabihf1.2.15indirect
npm@rolldown/binding-linux-arm64-gnu1.2.15indirect
npm@rolldown/binding-linux-arm64-musl1.2.15indirect
npm@rolldown/binding-linux-ppc64-gnu1.2.15indirect
npm@rolldown/binding-linux-s390x-gnu1.2.15indirect
npm@rolldown/binding-linux-x64-gnu1.2.15indirect
npm@rolldown/binding-linux-x64-musl1.2.15indirect
npm@rolldown/binding-openharmony-arm641.2.15indirect
npm@rolldown/binding-win32-arm64-msvc1.2.15indirect
npm@rolldown/binding-win32-x64-msvc1.2.15indirect
npm@rolldown/pluginutils1.0.1indirect
npm@standard-schema/spec1.1.0indirect
npm@types/better-sqlite37.6.13indirect
npm@types/chai5.2.3indirect
npm@types/deep-eql4.0.2indirect
npm@types/estree1.0.9indirect
npm@types/node26.1.0indirect
npm@types/pako2.0.4indirect
npm@vitest/expect4.1.12indirect
npm@vitest/mocker4.1.12indirect
npm@vitest/pretty-format4.1.12indirect
npm@vitest/runner4.1.12indirect
npm@vitest/snapshot4.1.12indirect
npm@vitest/spy4.1.12indirect
npm@vitest/utils4.1.12indirect
npmassertion-error2.0.1indirect
npmbase64-js1.5.1indirect
npmbetter-sqlite312.11.1indirect
npmbindings1.5.0indirect
npmbl4.1.0indirect
npmbuffer5.7.1indirect
npmchai6.3.0indirect
npmchownr1.1.4indirect
npmconvert-source-map2.0.0indirect
npmdecompress-response6.0.0indirect
npmdeep-extend0.6.0indirect
npmdetect-libc2.1.2indirect
npmend-of-stream1.4.5indirect
npmes-module-lexer2.2.0indirect
npmestree-walker3.0.3indirect
npmexpand-template2.0.3indirect
npmexpect-type1.4.0indirect
npmfdir6.5.0indirect
npmfile-uri-to-path1.0.0indirect
npmfs-constants1.0.0indirect
npmfsevents2.3.3indirect
npmfzstd0.1.1indirect
npmgithub-from-package0.0.0indirect
npmieee7541.2.1indirect
npminherits2.0.4indirect
npmini1.3.8indirect
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
npmmagic-string0.30.21indirect
npmmimic-response3.1.0indirect
npmminimist1.2.8indirect
npmmkdirp-classic0.5.3indirect
npmnanoid3.3.20indirect
npmnapi-build-utils2.0.0indirect
npmnode-abi3.94.0indirect
npmobug2.1.3indirect
npmonce1.4.0indirect
npmpako3.0.0indirect
npmpathe2.0.3indirect
npmpicocolors1.1.1indirect
npmpicomatch4.0.7indirect
npmpostcss8.5.32indirect
npmprebuild-install7.1.3indirect
npmprettier2.3.2indirect
npmpump3.0.4indirect
npmrc1.2.8indirect
npmreadable-stream3.6.2indirect
npmrolldown1.2.15indirect
npmsafe-buffer5.2.1indirect
npmsemver7.8.5indirect
npmsiginfo2.0.0indirect
npmsimple-concat1.0.1indirect
npmsimple-get4.0.1indirect
npmsource-map-js1.2.2indirect
npmstackback0.0.2indirect
npmstd-env4.1.0indirect
npmstring_decoder1.3.0indirect
npmstrip-json-comments2.0.1indirect
npmtar-fs2.1.5indirect
npmtar-stream2.2.0indirect
npmtinybench2.9.0indirect
npmtinyexec1.2.4indirect
npmtinyglobby0.2.17indirect
npmtinyrainbow3.2.0indirect
npmtunnel-agent0.6.0indirect
npmtypescript6.0.3indirect
npmundici-types8.3.0indirect
npmutil-deprecate1.0.2indirect
npmvite8.3.5indirect
npmvitest4.1.12indirect
npmwhy-is-node-running2.3.0indirect
npmwrappy1.0.2indirect
Dependency advisories 0

Installing npm:brs-js@4.0.5 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.