Public record
Software health reportschema 0.27.0 · metrics 2.10.0 · 2026-08-02 13:46 UTC

koodikulma-fi / dom-types

Repo for the "dom-types" npm module. Provides native and camelCase typing for DOM attributes and a couple of JS helpers.

TypeScriptMIT★ 2 stars⑂ 1 forksince Sep 2024View on GitHub ↗

koodikulma-fi/dom-types holds a health index of 29 out of 100, placing it in the At Risk band. It scores highest on Sustainability & Governance (54/100) and lowest on Engineering Quality (17/100). It was last updated 9 days ago. A single contributor accounts for most of its recent work.

29
overall / 100
At Risk

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.

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

Ownership

Mikael SaurenPersonal account
1 follower7 public repossince Jan 2016

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 publishTags
npmdom-types1.1.59,87679 days agodomtypesdom-typesdomtypestoolswebtsjstypescriptjavascriptlibrary

Metrics by category

Vitality

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

30At Risk · 21% of overall
How it's scored
28.8/36Push recencylast push 9 days ago
2.8/36Commit cadence4/52 weeks with commits
10.6/18Commit volume14 commits in the last year
8/10OpenSSF Scorecard: Maintained10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
Inputs used
commits_last_year14
human_commit_share1
days_since_last_push9
active_weeks_last_year4
How it's scored
0/27Ships releasesno releases published
0/36Release recencyno releases
0/27Release cadenceno releases
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count0
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?

35Weak · 17% of overall
How it's scored
0/60Stars2 stars
0/25Forks1 forks
0/15Watchers1 watchers
Inputs used
forks1
stars2
watchers1
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_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
53.3/80Monthly downloads9,876 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesdom-types
dependents
ecosystemsnpm
total_downloads
monthly_downloads9,876
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?

54Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.8/22.5Commit distributiontop contributor authored 97% of commits
2.7/13.5Contributor breadth2 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.966
How it's scored
42/42Issue resolution100% of issues closed
30/30PR acceptance3/3 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 3/28 approved changesets -- score normalized to 1
Inputs used
merged_prs3
open_issues0
closed_issues1
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs0
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
2.2/25Owner reach1 followers of koodikulma-fi
18.6/25Track record7 public repos, account ~10 yr old
Inputs used
followers1
owner_typeUser
is_verified
owner_loginkoodikulma-fi
public_repos7
account_age_days3,859
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 9 days ago
20/20Version history7 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesdom-types
ecosystemsnpm
any_deprecatedno
min_days_since_publish9

Engineering Quality

Are baseline engineering and documentation practices in place?

17Critical · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 3 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
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?

39Weak · 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-Tests0 out of 3 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.8/7.5Code-ReviewFound 3/28 approved changesets -- score normalized to 1
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
6/7.5Maintained10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
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
0/7.5Vulnerabilities12 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate2.4
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 advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories12
affected_packages5
assessed_packages95
unassessed_packages0
affected_by_severitycritical 1, high 4
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 95 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.

29At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
1.2/40Legible commit history2 of 89 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.022
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
11/11Static type checkingtsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 89
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_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
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
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/22 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes58,039
source_files_sampled22
oversized_source_files0

Key facts

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

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

OpenSSF Scorecard 2.4 / 10
2.4aggregate

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-08-02 13:46 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 3 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 3/28 approved changesets -- score normalized to 1
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
8Maintained10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
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
0Vulnerabilities12 existing vulnerabilities detected
All dependencies 95

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

RegistryPackageVersionRelation
npm@babel/code-frame7.24.7indirect
npm@babel/helper-validator-identifier7.24.7indirect
npm@babel/highlight7.24.7indirect
npm@jridgewell/gen-mapping0.3.5indirect
npm@jridgewell/resolve-uri3.1.2indirect
npm@jridgewell/set-array1.2.1indirect
npm@jridgewell/source-map0.3.6indirect
npm@jridgewell/sourcemap-codec1.5.0indirect
npm@jridgewell/trace-mapping0.3.25indirect
npm@nodelib/fs.scandir2.1.5indirect
npm@nodelib/fs.stat2.0.5indirect
npm@nodelib/fs.walk1.2.8indirect
npm@types/fs-extra8.1.5indirect
npm@types/glob7.2.0indirect
npm@types/minimatch5.1.2indirect
npm@types/node22.5.4indirect
npmacorn8.12.1indirect
npmaggregate-error3.1.0indirect
npmansi-styles3.2.1indirect
npmarray-union2.1.0indirect
npmbalanced-match1.0.2indirect
npmbrace-expansion1.1.11indirect
npmbraces3.0.3indirect
npmbuffer-from1.1.2indirect
npmchalk2.4.2indirect
npmclean-stack2.2.0indirect
npmcolor-convert1.9.3indirect
npmcolor-name1.1.3indirect
npmcolorette1.4.0indirect
npmcommander2.20.3indirect
npmconcat-map0.0.1indirect
npmdel5.1.0indirect
npmdir-glob3.0.1indirect
npmescape-string-regexp1.0.5indirect
npmfast-glob3.3.2indirect
npmfastq1.17.1indirect
npmfill-range7.1.1indirect
npmfs-extra8.1.0indirect
npmfs.realpath1.0.0indirect
npmfsevents2.3.3indirect
npmglob7.2.3indirect
npmglob-parent5.1.2indirect
npmglobby10.0.1indirect
npmglobby10.0.2indirect
npmgraceful-fs4.2.11indirect
npmhas-flag3.0.0indirect
npmhas-flag4.0.0indirect
npmignore5.3.2indirect
npmindent-string4.0.0indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npmis-extglob2.1.1indirect
npmis-glob4.0.3indirect
npmis-number7.0.0indirect
npmis-path-cwd2.2.0indirect
npmis-path-inside3.0.3indirect
npmis-plain-object3.0.1indirect
npmjest-worker26.6.2indirect
npmjs-tokens4.0.0indirect
npmjsonfile4.0.0indirect
npmmagic-string0.26.7indirect
npmmerge-stream2.0.0indirect
npmmerge21.4.1indirect
npmmicromatch4.0.8indirect
npmminimatch3.1.2indirect
npmonce1.4.0indirect
npmp-map3.0.0indirect
npmpath-is-absolute1.0.1indirect
npmpath-type4.0.0indirect
npmpicocolors1.1.0indirect
npmpicomatch2.3.1indirect
npmqueue-microtask1.2.3indirect
npmrandombytes2.1.0indirect
npmreusify1.0.4indirect
npmrimraf3.0.2indirect
npmrollup2.79.1indirect
npmrollup-plugin-copy3.5.0indirect
npmrollup-plugin-delete2.1.0indirect
npmrollup-plugin-dts4.2.3indirect
npmrollup-plugin-terser7.0.2indirect
npmrun-parallel1.2.0indirect
npmsafe-buffer5.2.1indirect
npmserialize-javascript4.0.0indirect
npmslash3.0.0indirect
npmsource-map0.6.1indirect
npmsource-map-support0.5.21indirect
npmsourcemap-codec1.4.8indirect
npmsupports-color5.5.0indirect
npmsupports-color7.2.0indirect
npmterser5.32.0indirect
npmto-regex-range5.0.1indirect
npmtypescript4.9.5indirect
npmundici-types6.19.8indirect
npmuniversalify0.1.2indirect
npmwrappy1.0.2indirect
Dependency advisories 5

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

PackageVersionRelationSeverityAdvisoriesFixed in
rollup2.79.1indirectcritical24.59.0
brace-expansion1.1.11indirecthigh45.0.8
minimatch3.1.2indirecthigh310.2.3
picomatch2.3.1indirecthigh24.0.4
serialize-javascript4.0.0indirecthigh17.0.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.

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.27.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsnpm.