Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-16 01:44 UTC

codenautas / type-store

type ecosystem

JavaScriptMIT★ 0 stars⑂ 0 forkssince Dec 2016View on GitHub ↗

codenautas/type-store holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (83/100) and lowest on Community & Adoption (32/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

CodenautasOrganization
5 followers140 public repossince Nov 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npmtype-store0.6.1864874 days ago

Metrics by category

Vitality

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

74Good · 21% of overall
How it's scored
36/36Push recencylast push 4 days ago
6.2/36Commit cadence9/52 weeks with commits
12.7/18Commit volume25 commits in the last year
10/10OpenSSF Scorecard: Maintained12 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year25
human_commit_share1
days_since_last_push4
active_weeks_last_year9
How it's scored
16.2/27Ships releases9 version tags (no GitHub releases)
36/36Release recencylatest release 54 days ago
27/27Release cadencea release every ~21.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count9
latest_release_tagv0.6.0
releases_from_tagsyes
days_since_latest_release54
mean_days_between_releases21.5
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?

32At Risk · 17% of overall
How it's scored
0/60Stars0 stars
0/25Forks0 forks
5.3/15Watchers10 watchers
Inputs used
forks0
stars0
watchers10
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_badges5
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
39.2/80Monthly downloads864 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagestype-store
dependents
ecosystemsnpm
total_downloads
monthly_downloads864
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?

55Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
7.9/22.5Commit distributiontop contributor authored 65% of commits
9.5/13.5Contributor breadth7 contributors
10/10OpenSSF Scorecard: Contributorsproject has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled7
top_contributor_share0.65
How it's scored
21/42Issue resolution50% of issues closed
0/30PR acceptanceno decided pull requests or no data
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues1
closed_issues1
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.5
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
5.6/25Owner reach5 followers of codenautas
25/25Track record140 public repos, account ~11 yr old
Inputs used
followers5
owner_typeOrganization
is_verifiedno
owner_logincodenautas
public_repos140
account_age_days4,320

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 4 days ago
20/20Version history87 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagestype-store
ecosystemsnpm
any_deprecatedno
min_days_since_publish4

Engineering Quality

Are baseline engineering and documentation practices in place?

83Excellent · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
16/16Linter config.eslintrc.yml
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
How it's scored
30/30README
25/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_diryes
has_descriptionyes

Security

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

50Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 5 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained12 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
4.5/7.5Vulnerabilities4 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate3.8
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 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_packages5
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:type-store@0.6.1 runtime dependency closure — what installing the published package pulls in — 5 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.

41Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history0 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.eslintrc.yml
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-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
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
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
55/55Manageable file sizes0/6 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes38,718
source_files_sampled6
oversized_source_files0
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 examplesexample
Inputs used
example_dirsexample
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
7contributors
25commits, last 12 months
4days since last push
9releases
1bus factor
1open issues
npmpackage ecosystems

More detail

OpenSSF Scorecard 3.8 / 10
3.8aggregate

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-16 01:44 UTC

10Binary-Artifactsno binaries found in the repo
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 5 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained12 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
6Vulnerabilities4 existing vulnerabilities detected
Direct dependencies 5
RegistryPackageVersion constraintManifest
npmbig.js^7.0.1package.json
npmbest-globals^2.2.2package.json
npmjs-to-html^1.3.6package.json
npmjson4all^1.4.4package.json
npmlike-ar^0.5.3package.json
All dependencies 124

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

RegistryPackageVersionRelation
npmbest-globals2.1.0direct
npmbig.js7.0.1direct
npmjs-to-html1.3.5direct
npmjson4all1.4.2direct
npmlike-ar0.5.2direct
npm@isaacs/cliui8.0.2indirect
npm@pkgjs/parseargs0.11.0indirect
npmabbrev1.0.9indirect
npmamdefine1.0.1indirect
npmansi-regex5.0.1indirect
npmansi-regex6.2.2indirect
npmansi-styles4.3.0indirect
npmansi-styles6.2.3indirect
npmargparse1.0.10indirect
npmargparse2.0.1indirect
npmasync1.5.2indirect
npmbalanced-match1.0.2indirect
npmbrace-expansion1.1.14indirect
npmbrace-expansion2.1.0indirect
npmbrowser-stdout1.3.1indirect
npmcamelcase6.3.0indirect
npmchalk4.1.2indirect
npmchokidar4.0.3indirect
npmcliui8.0.1indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmconcat-map0.0.1indirect
npmcross-spawn7.0.6indirect
npmdebug4.4.3indirect
npmdecamelize4.0.0indirect
npmdeep-is0.1.4indirect
npmdiff8.0.4indirect
npmdiscrepances0.2.9indirect
npmeastasianwidth0.2.0indirect
npmemoji-regex8.0.0indirect
npmemoji-regex9.2.2indirect
npmescalade3.2.0indirect
npmescape-string-regexp4.0.0indirect
npmescodegen1.8.1indirect
npmesprima2.7.3indirect
npmesprima4.0.1indirect
npmestraverse1.9.3indirect
npmesutils2.0.3indirect
npmexpect.js0.3.1indirect
npmfast-levenshtein2.0.6indirect
npmfind-up5.0.0indirect
npmflat5.0.2indirect
npmforeground-child3.3.1indirect
npmget-caller-file2.0.5indirect
npmglob10.5.0indirect
npmglob5.0.15indirect
npmhandlebars4.7.9indirect
npmhas-flag1.0.0indirect
npmhas-flag4.0.0indirect
npmhe1.2.0indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-path-inside3.0.3indirect
npmis-plain-obj2.1.0indirect
npmis-unicode-supported0.1.0indirect
npmisexe2.0.0indirect
npmistanbul0.4.5indirect
npmjackspeak3.4.3indirect
npmjs-yaml3.14.2indirect
npmjs-yaml4.1.1indirect
npmlevn0.3.0indirect
npmlocate-path6.0.0indirect
npmlog-symbols4.1.0indirect
npmlru-cache10.4.3indirect
npmminimatch3.1.5indirect
npmminimatch9.0.9indirect
npmminimist1.2.8indirect
npmminipass7.1.3indirect
npmmkdirp0.5.6indirect
npmmocha11.7.5indirect
npmms2.1.3indirect
npmneo-async2.6.2indirect
npmnopt3.0.6indirect
npmonce1.4.0indirect
npmoptionator0.8.3indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmpackage-json-from-dist1.0.1indirect
npmpath-exists4.0.0indirect
npmpath-is-absolute1.0.1indirect
npmpath-key3.1.1indirect
npmpath-scurry1.11.1indirect
npmpicocolors1.1.1indirect
npmpostgres-interval4.0.2indirect
npmprelude-ls1.1.2indirect
npmreaddirp4.1.2indirect
npmrequire-directory2.1.1indirect
npmresolve1.1.7indirect
npmserialize-javascript7.0.5indirect
npmshebang-command2.0.0indirect
npmshebang-regex3.0.0indirect
npmsignal-exit4.1.0indirect
npmsource-map0.2.0indirect
npmsource-map0.6.1indirect
npmsprintf-js1.0.3indirect
npmstring-width4.2.3indirect
npmstring-width5.1.2indirect
npmstrip-ansi6.0.1indirect
npmstrip-ansi7.2.0indirect
npmstrip-json-comments3.1.1indirect
npmsupports-color3.2.3indirect
npmsupports-color7.2.0indirect
npmsupports-color8.1.1indirect
npmtype-check0.3.2indirect
npmuglify-js3.19.3indirect
npmwhich1.3.1indirect
npmwhich2.0.2indirect
npmword-wrap1.2.5indirect
npmwordwrap1.0.0indirect
npmworkerpool9.3.4indirect
npmwrap-ansi7.0.0indirect
npmwrap-ansi8.1.0indirect
npmwrappy1.0.2indirect
npmy18n5.0.8indirect
npmyargs17.7.2indirect
npmyargs-parser21.1.1indirect
npmyargs-unparser2.0.0indirect
npmyocto-queue0.1.0indirect
Dependency advisories 0

Installing npm:type-store@0.6.1 pulls in 5 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.