Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-10 05:17 UTC

LeavittSoftware / titanium-elements

TypeScriptMIT★ 20 stars⑂ 0 forkssince Aug 2018View on GitHub ↗

LeavittSoftware/titanium-elements holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Engineering Quality (80/100) and lowest on Community & Adoption (42/100). It was last updated 8 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Leavitt SoftwareOrganization
1 follower12 public repossince Jan 2018

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmrootpoints to another repo — not scored3.2.012,571713053 days agolightweightwebroutingmixinhttp
npm@leavittsoftware/web11.4.12,2623018 days ago—

Metrics by category

Vitality

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

53Moderate · 21% of overall
How it's scored
28.8/36Push recency — last push 8 days ago
29.8/36Commit cadence — 43/52 weeks with commits
18/18Commit volume — 394 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year394
human_commit_share1
days_since_last_push8
active_weeks_last_year43
How it's scored
0/27Ships releases — no releases published
0/36Release recency — no releases
0/27Release cadence — no releases
0/10OpenSSF Scorecard: Signed-Releases — no 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?

42Weak · 17% of overall
How it's scored
20.7/60Stars — 20 stars
0/25Forks — 0 forks
5/15Watchers — 9 watchers
Inputs used
forks0
stars20
watchers9
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/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_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
44.7/80Monthly downloads — 2,262 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packages@leavittsoftware/web
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads2,262
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
5.2/22.5Commit distribution — top contributor authored 77% of commits
13.5/13.5Contributor breadth — 15 contributors
10/10OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled15
top_contributor_share0.768
How it's scored
41.7/42Issue resolution — 99% of issues closed
27.6/30PR acceptance — 434/471 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 1/29 approved changesets -- score normalized to 0
Inputs used
merged_prs434
open_issues2
closed_issues265
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.993
closed_unmerged_prs37
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
0/20Verified domain
2.2/25Owner reach — 1 followers of LeavittSoftware
20.1/25Track record — 12 public repos, account ~8 yr old
Inputs used
followers1
owner_typeOrganization
is_verifiedno
owner_loginLeavittSoftware
public_repos12
account_age_days3,144

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 8 days ago
20/20Version history — 301 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packages@leavittsoftware/web
ecosystemsnpm
any_deprecatedno
min_days_since_publish8

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.mjs, package.json ("prettier")
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 2 out of 2 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://storybook.leavitt.com
0/10Repository description
10/10Topics — 4 topics
10/10Wiki
Inputs used
topicshacktoberfest, lit-html, lit-element, webcomponents
has_wikiyes
homepagehttps://storybook.leavitt.com
docs_sitehttps://storybook.leavitt.com
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

62Moderate · 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
2.5/2.5CI-Tests — 2 out of 2 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 1/29 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 5 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
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
6.8/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.3
Excluded from scoring (no data or not applicable): 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
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_packages4
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:root@3.2.0 runtime dependency closure — what installing the published package pulls in — 4 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.

77Good · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md, packages/leavittbook/CLAUDE.md, packages/web/CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 96 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.96
agent_instruction_filesCLAUDE.md, packages/leavittbook/CLAUDE.md, packages/web/CLAUDE.md
agent_instruction_max_bytes96,806
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.mjs, package.json ("prettier")
11/11Static type checking — tsconfig.json
0/10Reproducible environment
10/10Demonstrated agent practice — 17 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0.17
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/218 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes59,592
source_files_sampled218
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 — demos
Inputs used
example_dirsdemos
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

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

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • npm package 'root' points at a different repository (https://github.com/mafintosh/root); excluded from ecosystem scoring

More detail

OpenSSF Scorecard 5.3 / 10
5.3aggregate

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-10 05:17 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests2 out of 2 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/29 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
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 21
RegistryPackageVersion constraintManifest
npm@leavittsoftware/lg-core-typescript^5.1342.0package.json
npm@material/web^2.4.1package.json
npmapi-viewer-element^1.0.0-pre.10package.json
npmcountup.js^2.10.0package.json
npmlit3.3.3package.json
npmpromise-parallel-throttle^3.5.0package.json
npmtslib^2.8.1package.json
npm@googlemaps/js-api-loader^2.1.1packages/web/package.json
npm@leavittsoftware/lg-core-typescript*packages/web/package.json
npm@lit/context^1.1.6packages/web/package.json
npm@material/web*packages/web/package.json
npm@types/google.maps*packages/web/package.json
npmbowser^2.14.1packages/web/package.json
npmcropperjs2.1.1packages/web/package.json
npmdayjs^1.11.21packages/web/package.json
npmexport-to-csv^1.4.0packages/web/package.json
npmfuse.js^7.4.2packages/web/package.json
npmjwt-decode^4.0.0packages/web/package.json
npmpromise-parallel-throttle^3.5.0packages/web/package.json
npmregexparam~3.0.0packages/web/package.json
npmtslib^2.8.1packages/web/package.json
All dependencies 43

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

RegistryPackageVersionRelation
npm@googlemaps/js-api-loader^2.1.1direct
npm@leavittsoftware/lg-core-typescript*direct
npm@leavittsoftware/lg-core-typescript^5.1342.0direct
npm@lit/context^1.1.6direct
npm@material/web*direct
npm@material/web^2.4.1direct
npm@types/google.maps*direct
npmapi-viewer-element^1.0.0-pre.10direct
npmbowser^2.14.1direct
npmcountup.js^2.10.0direct
npmcropperjs2.1.1direct
npmdayjs^1.11.21direct
npmexport-to-csv^1.4.0direct
npmfuse.js^7.4.2direct
npmjwt-decode^4.0.0direct
npmlit3.3.3direct
npmpromise-parallel-throttle^3.5.0direct
npmregexparam~3.0.0direct
npmtslib^2.8.1direct
npm@custom-elements-manifest/analyzer^0.11.0indirect
npm@eslint/eslintrc^3.3.5indirect
npm@eslint/js^10.0.1indirect
npm@rollup/plugin-node-resolve^16.0.3indirect
npm@rollup/plugin-terser^1.0.0indirect
npm@types/jasmine^6.0.0indirect
npm@typescript-eslint/eslint-plugin^8.62.0indirect
npm@typescript-eslint/parser^8.62.0indirect
npm@web/dev-server^0.4.6indirect
npm@web/rollup-plugin-html^3.1.0indirect
npm@web/rollup-plugin-import-meta-assets^2.3.3indirect
npmconcurrently^10.0.3indirect
npmeslint^10.5.0indirect
npmeslint-plugin-lit^2.3.1indirect
npmeslint-plugin-wc^3.1.0indirect
npmjasmine^6.3.0indirect
npmlerna^9.0.7indirect
npmlit-analyzer^2.0.3indirect
npmprettier^3.8.4indirect
npmrimraf^6.1.3indirect
npmrollup^4.62.2indirect
npmrollup-plugin-workbox^8.1.3indirect
npmtypescript^6.0.3indirect
npmvscode-css-languageservice^6.3.10indirect
Dependency advisories 0

Installing npm:root@3.2.0 pulls in 4 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.