Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-21 16:40 UTC

TF2Autobot / node-steam-tradeoffer-manager

Simple and sane Steam trade offer management

JavaScriptMIT★ 1 star⑂ 2 forkssince Feb 2021View on GitHub ↗

TF2Autobot/node-steam-tradeoffer-manager holds a health index of 45 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (64/100) and lowest on AI Readiness (28/100). It was last updated 43 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

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 publishTags
npm@tf2autobot/tradeoffer-manager2.20.106,1785243 days agosteamtradeofferstradeofferstrading

Metrics by category

Vitality

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

59Moderate · 21% of overall
How it's scored
18/36Push recency — last push 43 days ago
4.2/36Commit cadence — 6/52 weeks with commits
13.9/18Commit volume — 34 commits in the last year
3/10OpenSSF Scorecard: Maintained — 4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
Inputs used
commits_last_year34
human_commit_share1
days_since_last_push43
active_weeks_last_year6
How it's scored
16.2/27Ships releases — 100 version tags (no GitHub releases)
36/36Release recency — latest release 43 days ago
27/27Release cadence — a release every ~9.4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv2.20.10
releases_from_tagsyes
days_since_latest_release43
mean_days_between_releases9.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?

41Weak · 17% of overall
How it's scored
0/60Stars — 1 stars
0/25Forks — 2 forks
0/15Watchers — 1 watchers
Inputs used
forks2
stars1
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)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
50.5/80Monthly downloads — 6,178 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@tf2autobot/tradeoffer-manager
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads6,178
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?

64Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
6.7/22.5Commit distribution — top contributor authored 70% of commits
13.5/13.5Contributor breadth — 21 contributors
10/10OpenSSF Scorecard: Contributors — project has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled21
top_contributor_share0.703
How it's scored
0/42Issue resolution — no issues or no data
21.4/30PR acceptance — 5/7 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/26 approved changesets -- score normalized to 0
Inputs used
merged_prs5
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs2
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
8.7/25Owner reach — 15 followers of TF2Autobot
22.5/25Track record — 27 public repos, account ~5 yr old
Inputs used
followers15
owner_typeOrganization
is_verifiedyes
owner_loginTF2Autobot
public_repos27
account_age_days2,176

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 43 days ago
20/20Version history — 52 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@tf2autobot/tradeoffer-manager
ecosystemsnpm
any_deprecatedno
min_days_since_publish43

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
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_testsno
has_editorconfigyes
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://dev.doctormckay.com/forum/9-node-steam-tradeoffer-manager/
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepagehttps://dev.doctormckay.com/forum/9-node-steam-tradeoffer-manager/
docs_sitehttps://dev.doctormckay.com/forum/9-node-steam-tradeoffer-manager/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

38Weak · 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/26 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 6 contributing companies or organizations
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
2.2/7.5Maintained — 4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
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.8/7.5Vulnerabilities — 9 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate2.2
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_packages73
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/tradeoffer-manager@2.20.10 runtime dependency closure — what installing the published package pulls in — 73 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.

28At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
1.1/40Legible commit history — 2 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.02
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
0/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 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
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/16 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes25,619
source_files_sampled16
oversized_source_files0
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

1GitHub stars
21contributors
34commits, last 12 months
43days since last push
100releases
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 ★ / 2 ⇿
0Stars
2Forks
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.

111222212024-042024-042024-04
Major 0Minor 0Patch 6
OpenSSF Scorecard 2.2 / 10
2.2aggregate

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-21 16:40 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/26 approved changesets -- score normalized to 0
10Contributorsproject has 6 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
3Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
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
1Vulnerabilities9 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
npm@doctormckay/stdlib^1.16.1package.json
npm@tf2autobot/steamcommunity^3.50.9package.json
npmasync^3.2.6package.json
npmfile-manager^2.0.1package.json
npmlanguages^0.1.3package.json
npmsteamid^2.1.0package.json
All dependencies 74

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

RegistryPackageVersionRelation
npm@doctormckay/stdlib1.16.1direct
npm@doctormckay/stdlib2.10.0direct
npm@tf2autobot/steamcommunity3.50.0direct
npmasync3.2.6direct
npmfile-manager2.0.1direct
npmlanguages0.1.3direct
npmsteamid2.1.0direct
npm@doctormckay/user-agents1.1.0indirect
npm@protobufjs/aspromise1.1.2indirect
npm@protobufjs/base641.1.2indirect
npm@protobufjs/codegen2.0.5indirect
npm@protobufjs/eventemitter1.1.1indirect
npm@protobufjs/fetch1.1.1indirect
npm@protobufjs/float1.0.2indirect
npm@protobufjs/path1.1.2indirect
npm@protobufjs/pool1.1.0indirect
npm@protobufjs/utf81.1.2indirect
npm@types/node26.1.0indirect
npmagent-base6.0.2indirect
npmboolbase1.0.0indirect
npmbytebuffer5.0.1indirect
npmcheerio1.2.0indirect
npmcheerio-select2.1.0indirect
npmcss-select5.2.2indirect
npmcss-what6.2.2indirect
npmdebug4.4.3indirect
npmdom-serializer2.0.0indirect
npmdomelementtype2.3.0indirect
npmdomhandler5.0.3indirect
npmdomutils3.2.2indirect
npmencoding-sniffer0.2.1indirect
npmentities4.5.0indirect
npmentities6.0.1indirect
npmentities7.0.1indirect
npmfetch-cookie3.2.0indirect
npmhtmlparser210.1.0indirect
npmiconv-lite0.6.3indirect
npmimage-size0.8.3indirect
npminherits2.0.4indirect
npmip-address10.2.0indirect
npmkvparser1.0.2indirect
npmlong3.2.0indirect
npmlong5.3.2indirect
npmms2.1.3indirect
npmnode-bignumber1.2.2indirect
npmnth-check2.1.1indirect
npmparse57.3.0indirect
npmparse5-htmlparser2-tree-adapter7.1.0indirect
npmparse5-parser-stream7.1.2indirect
npmpermessage-deflate0.1.7indirect
npmprotobufjs7.6.5indirect
npmpsl1.9.0indirect
npmqueue6.0.1indirect
npmsafe-buffer5.2.1indirect
npmsafer-buffer2.1.2indirect
npmsax1.3.0indirect
npmset-cookie-parser2.7.2indirect
npmsmart-buffer4.2.0indirect
npmsocks2.8.9indirect
npmsocks-proxy-agent7.0.0indirect
npmsteam-session1.9.4indirect
npmsteam-totp2.1.2indirect
npmtiny-typed-emitter2.1.0indirect
npmtldts7.4.8indirect
npmtldts-core7.4.8indirect
npmtough-cookie6.0.2indirect
npmundici7.28.0indirect
npmundici-types8.3.0indirect
npmwebsocket-extensions0.1.4indirect
npmwebsocket134.1.0indirect
npmwhatwg-encoding3.1.1indirect
npmwhatwg-mimetype4.0.0indirect
npmxml2js0.6.2indirect
npmxmlbuilder11.0.1indirect
Dependency advisories 0

Installing npm:@tf2autobot/tradeoffer-manager@2.20.10 pulls in 73 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.