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

TF2Autobot / node-bptf-listings

Manage listings on backpack.tf

JavaScriptMIT★ 0 stars⑂ 6 forkssince Nov 2021View on GitHub ↗

TF2Autobot/node-bptf-listings holds a health index of 53 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (68/100) and lowest on Engineering Quality (30/100). It was last updated 37 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

TF2AutobotOrganization · verified domain
15 followers27 public repossince Dec 2020

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npm@tf2autobot/bptf-listings5.9.61,7938037 days ago

Metrics by category

Vitality

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

62Moderate · 21% of overall
How it's scored
18/36Push recencylast push 37 days ago
4.8/36Commit cadence7/52 weeks with commits
12.6/18Commit volume24 commits in the last year
10/10OpenSSF Scorecard: Maintained23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year24
human_commit_share1
days_since_last_push37
active_weeks_last_year7
How it's scored
16.2/27Ships releases80 version tags (no GitHub releases)
36/36Release recencylatest release 37 days ago
27/27Release cadencea release every ~3.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count80
latest_release_tagv5.9.6
releases_from_tagsyes
days_since_latest_release37
mean_days_between_releases3.4
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?

33At Risk · 17% of overall
How it's scored
0/60Stars0 stars
5.8/25Forks6 forks
0/15Watchers0 watchers
Inputs used
forks6
stars0
watchers0
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
43.4/80Monthly downloads1,793 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@tf2autobot/bptf-listings
dependents
ecosystemsnpm
total_downloads
monthly_downloads1,793
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?

68Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
9.5/22.5Commit distributiontop contributor authored 58% of commits
12.2/13.5Contributor breadth9 contributors
10/10OpenSSF Scorecard: Contributorsproject has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled9
top_contributor_share0.576
How it's scored
28/42Issue resolution67% of issues closed
26.7/30PR acceptance8/9 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/26 approved changesets -- score normalized to 0
Inputs used
merged_prs8
open_issues1
closed_issues2
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.667
closed_unmerged_prs1
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
30/30Ownership backingorganization-owned
20/20Verified domain
8.7/25Owner reach15 followers of TF2Autobot
22.1/25Track record27 public repos, account ~5 yr old
Inputs used
followers15
owner_typeOrganization
is_verifiedyes
owner_loginTF2Autobot
public_repos27
account_age_days2,107

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 37 days ago
20/20Version history80 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@tf2autobot/bptf-listings
ecosystemsnpm
any_deprecatedno
min_days_since_publish37

Engineering Quality

Are baseline engineering and documentation practices in place?

30At Risk · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
16/16Linter config.eslintrc
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 2 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configyes
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?

65Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0/2.5CI-Tests0 out of 2 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 0/26 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 6 contributing companies or organizations
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
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-Releasesno data
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate5.6
Excluded from scoring (no data or not applicable): Branch-Protection, 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 advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages47
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:@tf2autobot/bptf-listings@5.9.6 runtime dependency closure — what installing the published package pulls in — 47 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.

32At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
3.2/40Legible commit history6 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.06
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
0/22Automated tests
11/11Lint / format config.eslintrc
0/11Static type checking
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
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
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 codeJavaScript without a type-check config
48.9/55Manageable file sizes1/9 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes73,559
source_files_sampled9
oversized_source_files1
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
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

0GitHub stars
9contributors
24commits, last 12 months
37days since last push
80releases
1bus factor
1open issues
npmpackage ecosystems

More detail

Star and fork history 0 ★ / 6 ⇿
0Stars
6Forks
11Releases

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.

1223344412023-062024-072025-08
Major 0Minor 1Patch 10

Each point covers 3 days.

OpenSSF Scorecard 5.6 / 10
5.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-13 16:43 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
0CI-Tests0 out of 2 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/26 approved changesets -- score normalized to 0
10Contributorsproject has 6 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained23 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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 8
RegistryPackageVersion constraintManifest
npm@tf2autobot/tf2-currencies^2.0.1package.json
npm@tf2autobot/tf2-sku^3.1.0package.json
npmasync^3.2.6package.json
npmevents^3.3.0package.json
npmhttps-proxy-agent^7.0.6package.json
npmsteamid^2.1.0package.json
npmundici^8.10.0package.json
npmutil^0.12.5package.json
All dependencies 57

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

RegistryPackageVersionRelation
npm@tf2autobot/tf2-currencies2.0.1direct
npm@tf2autobot/tf2-sku2.0.4direct
npmasync3.2.6direct
npmevents3.3.0direct
npmhttps-proxy-agent5.0.1direct
npmhttps-proxy-agent7.0.6direct
npmsteamid2.1.0direct
npmutil0.12.5direct
npm@tf2autobot/filter-axios-error1.5.6indirect
npmagent-base6.0.2indirect
npmagent-base7.1.4indirect
npmasynckit0.4.0indirect
npmavailable-typed-arrays1.0.7indirect
npmaxios1.18.1indirect
npmcall-bind1.0.8indirect
npmcall-bind-apply-helpers1.0.2indirect
npmcall-bound1.0.4indirect
npmclone1.0.4indirect
npmcombined-stream1.0.8indirect
npmdebug4.4.3indirect
npmdefaults1.0.4indirect
npmdefine-data-property1.1.4indirect
npmdelayed-stream1.0.0indirect
npmdunder-proto1.0.1indirect
npmes-define-property1.0.1indirect
npmes-errors1.3.0indirect
npmes-object-atoms1.1.2indirect
npmes-set-tostringtag2.1.0indirect
npmfollow-redirects1.16.0indirect
npmfor-each0.3.5indirect
npmform-data4.0.6indirect
npmfunction-bind1.1.2indirect
npmgenerator-function2.0.1indirect
npmget-intrinsic1.3.0indirect
npmget-proto1.0.1indirect
npmgopd1.2.0indirect
npmhas-property-descriptors1.0.2indirect
npmhas-symbols1.1.0indirect
npmhas-tostringtag1.0.2indirect
npmhasown2.0.4indirect
npminherits2.0.4indirect
npmis-arguments1.2.0indirect
npmis-callable1.2.7indirect
npmis-generator-function1.1.2indirect
npmis-regex1.2.1indirect
npmis-typed-array1.1.15indirect
npmmath-intrinsics1.1.0indirect
npmmime-db1.52.0indirect
npmmime-types2.1.35indirect
npmms2.1.3indirect
npmobject-prettify1.0.0indirect
npmpluralize8.0.0indirect
npmpossible-typed-array-names1.1.0indirect
npmproxy-from-env2.1.0indirect
npmsafe-regex-test1.1.0indirect
npmset-function-length1.2.2indirect
npmwhich-typed-array1.1.19indirect
Dependency advisories 0

Installing npm:@tf2autobot/bptf-listings@5.9.6 pulls in 47 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 statisticsnpm.