Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-21 12:24 UTC

calamity-inc / warframe-public-export-plus

The most complete data source for all your Warframe needs and interests. Contains everything missing in Public Export and more.

JSONMIT★ 71 stars⑂ 17 forkssince Jun 2024View on GitHub ↗

calamity-inc/warframe-public-export-plus holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Vitality (89/100) and lowest on AI Readiness (20/100). It was last updated 5 days ago. A single contributor accounts for most of its recent work.

71
overall / 100
Good

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.

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

Ownership

Calamity, Inc.Organization · verified domain
74 followers74 public repossince Apr 2022

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npmwarframe-public-export-plus0.6.124,96314215 days ago

Metrics by category

Vitality

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

89Excellent · 21% of overall
How it's scored
36/36Push recency — last push 5 days ago
24.9/36Commit cadence — 36/52 weeks with commits
18/18Commit volume — 172 commits in the last year
10/10OpenSSF Scorecard: Maintained — 20 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year172
human_commit_share0.97
days_since_last_push5
active_weeks_last_year36
How it's scored
16.2/27Ships releases — 100 version tags (no GitHub releases)
36/36Release recency — latest release 15 days ago
27/27Release cadence — a release every ~11 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tag0.6.12
releases_from_tagsyes
days_since_latest_release15
mean_days_between_releases11
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?

57Moderate · 17% of overall
How it's scored
29.9/60Stars — 71 stars
10/25Forks — 17 forks
2.7/15Watchers — 4 watchers
Inputs used
forks17
stars71
watchers4
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_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
49.3/80Monthly downloads — 4,963 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageswarframe-public-export-plus
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads4,963
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
0.3/22.5Commit distribution — top contributor authored 99% of commits
4.1/13.5Contributor breadth — 3 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.987
How it's scored
37/42Issue resolution — 88% of issues closed
19.1/30PR acceptance — 7/11 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs7
open_issues9
closed_issues67
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.882
closed_unmerged_prs4
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 backing — organization-owned
20/20Verified domain
13.5/25Owner reach — 74 followers of calamity-inc
22.1/25Track record — 74 public repos, account ~4 yr old
Inputs used
followers74
owner_typeOrganization
is_verifiedyes
owner_logincalamity-inc
public_repos74
account_age_days1,659

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 15 days ago
20/20Version history — 142 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageswarframe-public-export-plus
ecosystemsnpm
any_deprecatedno
min_days_since_publish15

Engineering Quality

Are baseline engineering and documentation practices in place?

48Weak · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://www.npmjs.com/package/warframe-public-export-plus
10/10Repository description
10/10Topics — 2 topics
10/10Wiki
Inputs used
topicswarframe, warframe-items
has_wikiyes
homepagehttps://www.npmjs.com/package/warframe-public-export-plus
docs_sitehttps://www.npmjs.com/package/warframe-public-export-plus
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

61Moderate · 16% of overall
How it's scored
6.8/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 20 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
1.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.1
Excluded from scoring (no data or not applicable): CI-Tests, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages100
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 100 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

20At 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.6/40Legible commit history — 3 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.031
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
8/8Automated maintenance — 3 of the last 100 commits are automated dependency updates
3/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
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.03
How it's scored
0/45Type-checkable code — JSON without a type-check config
55/55Manageable file sizes — 0/5 source files over 60KB
Inputs used
primary_languageJSON
largest_source_bytes34,009
source_files_sampled5
oversized_source_files0

Key facts

71GitHub stars
3contributors
172commits, last 12 months
5days since last push
100releases
1bus factor
9open 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 ★ / 17 ⇿
0Stars
17Forks
40Releases

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.

0481216201712025-072026-022026-10
Major 0Minor 1Patch 39

Each point covers 2 days.

OpenSSF Scorecard 5.1 / 10
5.1aggregate

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-10-21 12:24 UTC

9Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained20 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 100

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

RegistryPackageVersionRelation
npm@clack/core1.0.0-alpha.4indirect
npm@clack/prompts1.0.0-alpha.4indirect
npm@oclif/core4.13.0indirect
npm@typescript/vfs1.6.1indirect
npmansi-escapes4.3.2indirect
npmansi-escapes7.3.0indirect
npmansi-regex5.0.1indirect
npmansi-regex6.2.2indirect
npmansi-styles4.3.0indirect
npmansi-styles6.2.3indirect
npmansis3.17.0indirect
npmasync3.2.6indirect
npmbalanced-match1.0.2indirect
npmbalanced-match4.0.4indirect
npmbrace-expansion2.1.7indirect
npmbrace-expansion5.0.12indirect
npmchokidar4.0.3indirect
npmclean-stack3.0.1indirect
npmcli-cursor5.0.0indirect
npmcli-spinners2.9.2indirect
npmcli-truncate5.2.0indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcolorette2.0.20indirect
npmdebug4.4.3indirect
npmejs3.1.10indirect
npmemoji-regex10.6.0indirect
npmemoji-regex8.0.0indirect
npmenvironment1.1.0indirect
npmescape-string-regexp4.0.0indirect
npmeventemitter35.0.4indirect
npmfdir6.5.0indirect
npmfilelist1.0.6indirect
npmget-east-asian-width1.6.0indirect
npmget-package-type0.1.0indirect
npmhas-flag4.0.0indirect
npmindent-string4.0.0indirect
npmis-docker2.2.1indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-fullwidth-code-point5.1.0indirect
npmis-wsl2.2.0indirect
npmjake10.9.4indirect
npmlilconfig3.1.3indirect
npmlistr29.0.5indirect
npmlog-update6.1.0indirect
npmmimic-function5.0.1indirect
npmminimatch10.2.5indirect
npmminimatch5.1.9indirect
npmms2.1.3indirect
npmonetime7.0.0indirect
npmpicocolors1.1.1indirect
npmpicomatch4.0.5indirect
npmreaddirp4.1.2indirect
npmrestore-cursor5.1.0indirect
npmrfdc1.4.1indirect
npmsemver7.8.5indirect
npmsignal-exit4.1.0indirect
npmsisteransi1.0.5indirect
npmslash5.1.0indirect
npmslice-ansi7.1.2indirect
npmslice-ansi8.0.0indirect
npmstring-width4.2.3indirect
npmstring-width7.2.0indirect
npmstring-width8.2.2indirect
npmstrip-ansi6.0.1indirect
npmstrip-ansi7.2.0indirect
npmsupports-color8.1.1indirect
npmtext-camel-case1.2.11indirect
npmtext-capital-case1.2.11indirect
npmtext-case1.2.11indirect
npmtext-constant-case1.2.11indirect
npmtext-dot-case1.2.11indirect
npmtext-header-case1.2.11indirect
npmtext-is-lower-case1.2.11indirect
npmtext-is-upper-case1.2.11indirect
npmtext-kebab-case1.2.11indirect
npmtext-lower-case1.2.11indirect
npmtext-lower-case-first1.2.11indirect
npmtext-no-case1.2.11indirect
npmtext-param-case1.2.11indirect
npmtext-pascal-case1.2.11indirect
npmtext-path-case1.2.11indirect
npmtext-sentence-case1.2.11indirect
npmtext-snake-case1.2.11indirect
npmtext-swap-case1.2.11indirect
npmtext-title-case1.2.11indirect
npmtext-upper-case1.2.11indirect
npmtext-upper-case-first1.2.11indirect
npmtinyglobby0.2.17indirect
npmts-to-zod5.1.0indirect
npmtslib1.14.1indirect
npmtslib2.8.1indirect
npmtsutils3.21.0indirect
npmtype-fest0.21.3indirect
npmtypescript5.9.2indirect
npmwidest-line3.1.0indirect
npmwordwrap1.0.0indirect
npmwrap-ansi7.0.0indirect
npmwrap-ansi9.0.2indirect
npmzod4.4.3indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 100 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct.

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.