Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-11 15:15 UTC

idinium96 / node-steam-openid-login-dayjs

JavaScriptMIT★ 0 stars⑂ 0 forkssince Dec 2020View on GitHub ↗
KindLibraryhow this is determined

idinium96/node-steam-openid-login-dayjs holds a health index of 11 out of 100, placing it in the Critical band. It scores highest on Sustainability & Governance (38/100) and lowest on Community & Adoption (12/100). It was last updated 161 days ago. A single contributor accounts for most of its recent work.

11
overall / 100
Critical

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.

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

Ownership

IdiNiumPersonal account
34 followers23 public repossince Feb 2019@TF2Autobot

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 publish
npmsteam-openid-login-dayjspoints to another repo — not scored1.1.187121575 days ago

Metrics by category

Vitality

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

25At Risk · 21% of overall

Development activity

10Critical
How it's scored
9.9/36Push recency — last push 161 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_share0.867
days_since_last_push161
active_weeks_last_year0

Release discipline

48Weak
How it's scored
16.2/27Ships releases — 12 version tags (no GitHub releases)
0/36Release recency — latest release 1,575 days ago
27/27Release cadence — a release every ~41.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count12
latest_release_tagv1.1.1
releases_from_tagsyes
days_since_latest_release1,575
mean_days_between_releases41.6
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?

12Critical · 17% of overall

Popularity & adoption

1Critical
How it's scored
0/60Stars — 0 stars
0/25Forks — 0 forks
0/15Watchers — 1 watchers
Inputs used
forks0
stars0
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

25At Risk
How it's scored
0/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_readmeno
has_licenseyes
readme_badges—
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

38Weak · 23% of overall

Maintainer resilience (bus factor)

20At Risk
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
2.3/22.5Commit distribution — top contributor authored 90% of commits
2.7/13.5Contributor breadth — 2 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.897

Issue & PR responsiveness

44Weak
How it's scored
0/42Issue resolution — no issues or no data
20/30PR acceptance — 6/9 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_prs6
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs3
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.

Ownership & stewardship

54Moderate
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
11.1/25Owner reach — 34 followers of idinium96
22.1/25Track record — 23 public repos, account ~7 yr old
Inputs used
followers34
owner_typeUser
is_verified—
owner_loginidinium96
public_repos23
account_age_days2,766
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

14Critical · 19% of overall

Engineering practices

16Critical
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-Tests — 0 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

10Critical
How it's scored
0/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_site—
has_readmeno
has_docs_dirno
has_descriptionno

Security

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

34At Risk · 16% of overall

Security posture

27At Risk
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 2 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
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
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 — 10 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate2.7
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

63Moderate
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
6.1/25Indirect dependencies free of known advisories — 5 affected: form-data 2.3.3 (high 7.5), uuid 3.4.0 (high 7.5), qs 6.5.5 (moderate 5.3), +2 more
21.9/40No advisories left outstanding — 5 advisory-carrying package(s) unaddressed past 90 days; oldest published 1,274 days ago
Inputs used
sourceosv
advisories7
affected_packages5
assessed_packages74
unassessed_packages0
affected_by_severityhigh 2, moderate 3
direct_affected_packages0
Matched the npm:steam-openid-login-dayjs@1.1.1 runtime dependency closure — what installing the published package pulls in — 74 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

Agent context & guidance

8Critical
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
8.2/40Legible commit history — 6 of 39 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.154
agent_instruction_files—
agent_instruction_max_bytes—

Verify loop (build / test / typecheck)

32At Risk
How it's scored
0/18One-command bootstrap
0/22Automated tests
11/11Lint / format config — .eslintrc
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 45
8/8Automated maintenance — 6 of the last 45 commits are automated dependency updates
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_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.133
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.

Code legibility for models

55Moderate
How it's scored
0/45Type-checkable code — JavaScript without a type-check config
55/55Manageable file sizes — 0/1 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes2,875
source_files_sampled1
oversized_source_files0

Key facts

0GitHub stars
2contributors
0commits, last 12 months
161days since last push
12releases
1bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • npm package 'steam-openid-login-dayjs' points at a different repository (https://github.com/idinium96/node-steam-openid-login-2); excluded from ecosystem scoring

More detail

OpenSSF Scorecard 2.7 / 10
2.7aggregate

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-11 15:14 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
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
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
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
0Vulnerabilities10 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmcheerio^1.0.0-rc.10package.json
npmrequest-retry-dayjs^1.1.3package.json
All dependencies 67

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

RegistryPackageVersionRelation
npmcheerio1.0.0-rc.10direct
npmrequest-retry-dayjs1.1.3direct
npmajv6.12.6indirect
npmasn10.2.6indirect
npmassert-plus1.0.0indirect
npmasynckit0.4.0indirect
npmaws-sign20.7.0indirect
npmaws41.11.0indirect
npmbcrypt-pbkdf1.0.2indirect
npmboolbase1.0.0indirect
npmcaseless0.12.0indirect
npmcheerio-select1.5.0indirect
npmcombined-stream1.0.8indirect
npmcore-util-is1.0.2indirect
npmcss-select4.1.3indirect
npmcss-what5.0.1indirect
npmdashdash1.14.1indirect
npmdayjs1.11.2indirect
npmdelayed-stream1.0.0indirect
npmdom-serializer1.3.2indirect
npmdomelementtype2.2.0indirect
npmdomhandler4.2.0indirect
npmdomutils2.7.0indirect
npmecc-jsbn0.1.2indirect
npmentities2.2.0indirect
npmextend3.0.2indirect
npmextsprintf1.3.0indirect
npmfast-deep-equal3.1.3indirect
npmfast-json-stable-stringify2.1.0indirect
npmforever-agent0.6.1indirect
npmform-data2.3.3indirect
npmgetpass0.1.7indirect
npmhar-schema2.0.0indirect
npmhar-validator5.1.5indirect
npmhtmlparser26.1.0indirect
npmhttp-signature1.2.0indirect
npmhttp-status1.5.2indirect
npmis-typedarray1.0.0indirect
npmisstream0.1.2indirect
npmjsbn0.1.1indirect
npmjson-schema0.4.0indirect
npmjson-schema-traverse0.4.1indirect
npmjson-stringify-safe5.0.1indirect
npmjsprim1.4.2indirect
npmlodash4.17.21indirect
npmmime-db1.52.0indirect
npmmime-types2.1.35indirect
npmnth-check2.0.1indirect
npmoauth-sign0.9.0indirect
npmparse56.0.1indirect
npmparse5-htmlparser2-tree-adapter6.0.1indirect
npmperformance-now2.1.0indirect
npmpsl1.8.0indirect
npmpunycode2.1.1indirect
npmqs6.5.3indirect
npmrequest2.88.2indirect
npmrequestretry7.1.0indirect
npmsafe-buffer5.2.1indirect
npmsafer-buffer2.1.2indirect
npmsshpk1.17.0indirect
npmtough-cookie2.5.0indirect
npmtslib2.2.0indirect
npmtunnel-agent0.6.0indirect
npmtweetnacl0.14.5indirect
npmuri-js4.4.1indirect
npmuuid3.4.0indirect
npmverror1.10.0indirect
Dependency advisories 5

Installing npm:steam-openid-login-dayjs@1.1.1 pulls in 74 packages, direct and transitive: 5 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
form-data2.3.3indirecthigh24.0.6
uuid3.4.0indirecthigh113.0.1
qs6.5.5indirectmoderate26.16.0
request2.88.2indirectmoderate13.0.0
tough-cookie2.5.0indirectmoderate14.1.3

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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with idinium96/node-steam-openid-login-dayjs. Read them side by side →

100microsoft/onnxruntimeONNX Runtime: cross-platform, high performance ML inferencing and training acceleratorExceptional100risingwavelabs/risingwaveEvent streaming platform for agentic AI. Continuously ingest, transform, and serve event streams in real time, at scale.Exceptional100PrefectHQ/prefectPrefect is a workflow orchestration framework for building resilient data pipelines in Python.Exceptional100hashicorp/consulConsul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.Exceptional100supabase/supabase-jsAn isomorphic Javascript client for Supabase. Query your Supabase database, subscribe to realtime events, upload and download files, browse typescript examples, invoke postgres functions via rpc, invoke supabase edge functions, query pgvector.Exceptional100apache/airflowApache Airflow - A platform to programmatically author, schedule, and monitor workflowsExceptional

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.