Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-27 07:22 UTC

andymai / brepkit

B-Rep modeling engine for brepjs — pure Rust, compiled to WebAssembly

RustAGPL-3.0★ 31 stars⑂ 5 forkssince Mar 2026View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

andymai/brepkit holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Vitality (91/100) and lowest on Community & Adoption (53/100). It was last updated today. A single contributor accounts for most of its recent work.

86
overall / 100
Excellent

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.

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

Ownership

Andy AragonPersonal account
52 followers25 public repossince Mar 2010@babylist

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

Metrics by category

Vitality

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

91Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
20.8/36Commit cadence — 30/52 weeks with commits
18/18Commit volume — 1,818 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 15 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,818
human_commit_share0.53
days_since_last_push0
active_weeks_last_year30

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~0 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv4.0.54
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases0
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?

53Moderate · 17% of overall
How it's scored
24/60Stars — 31 stars
5/25Forks — 5 forks
0/15Watchers — 1 watchers
Inputs used
forks5
stars31
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (AGPL-3.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges8
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
53.9/80Monthly downloads — 11,048 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesbrepkit-io, brepkit-algo, brepkit-heal, brepkit-math, brepkit-wasm, brepkit-blend, brepkit-check
dependents—
ecosystemscrates
total_downloads33,144
monthly_downloads11,048
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?

59Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
2.7/13.5Contributor breadth — 2 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.998
How it's scored
42/42Issue resolution — 100% of issues closed
29.5/30PR acceptance — 1,700/1,731 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_prs1,700
open_issues0
closed_issues94
prs_merged_7d32
prs_decided_7d32
prs_merged_30d32
prs_decided_30d32
issue_closed_ratio1
closed_unmerged_prs31
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
12.4/25Owner reach — 52 followers of andymai
22.3/25Track record — 25 public repos, account ~16 yr old
Inputs used
followers52
owner_typeUser
is_verified—
owner_loginandymai
public_repos25
account_age_days6,049
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 7 package(s) on crates
35/35Publish recency — latest publish 0 days ago
20/20Version history — 132 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesbrepkit-io, brepkit-algo, brepkit-heal, brepkit-math, brepkit-wasm, brepkit-blend, brepkit-check
ecosystemscrates
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows — 6 workflow(s)
24/24Tests present
16/16Linter config — Cargo.toml ([workspace.lints]), clippy.toml, crates/algo/Cargo.toml ([lints]), crates/blend/Cargo.toml ([lints]), crates/check/Cargo.toml ([lints]), crates/geometry/Cargo.toml ([lints]), crates/heal/Cargo.toml ([lints]), crates/io/Cargo.toml ([lints]), crates/math/Cargo.toml ([lints]), crates/offset/Cargo.toml ([lints]), crates/operations/Cargo.toml ([lints]), crates/render/Cargo.toml ([lints]), crates/sketch/Cargo.toml ([lints]), crates/topology/Cargo.toml ([lints]), crates/wasm/Cargo.toml ([lints]), eslint.config.js
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 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://brepjs.dev
10/10Repository description
10/10Topics — 8 topics
0/10Wiki
Inputs used
topicsb-rep, brep, cad, geometry-kernel, rust, solid-modeling, wasm, webassembly
has_wikino
homepagehttps://brepjs.dev
docs_sitehttps://brepjs.dev
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

75Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 30 out of 30 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 0/30 approved changesets -- score normalized to 0
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
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 — 30 commit(s) and 15 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
4.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 9
5/5SAST — SAST tool is run on all commits
5/5Security-Policy — security policy file 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_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate6.9
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
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_packages94
unassessed_packages16
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 94 resolved dependencies against OSV. 16 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

87Excellent · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 53 of 53 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes31,137
How it's scored
12.6/18One-command bootstrap — Cargo.toml, crates/algo/Cargo.toml, crates/blend/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config — Cargo.toml ([workspace.lints]), clippy.toml, crates/algo/Cargo.toml ([lints]), crates/blend/Cargo.toml ([lints]), crates/check/Cargo.toml ([lints]), crates/geometry/Cargo.toml ([lints]), crates/heal/Cargo.toml ([lints]), crates/io/Cargo.toml ([lints]), crates/math/Cargo.toml ([lints]), crates/offset/Cargo.toml ([lints]), crates/operations/Cargo.toml ([lints]), crates/render/Cargo.toml ([lints]), crates/sketch/Cargo.toml ([lints]), crates/topology/Cargo.toml ([lints]), crates/wasm/Cargo.toml ([lints]), eslint.config.js
11/11Static type checking — bindings/ts/tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
9/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 9
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configsbindings/ts/tsconfig.json
agent_commit_share0
toolchain_manifestsCargo.toml, crates/algo/Cargo.toml, crates/blend/Cargo.toml, crates/check/Cargo.toml, crates/geometry/Cargo.toml, crates/heal/Cargo.toml, crates/io/Cargo.toml, crates/math/Cargo.toml, crates/offset/Cargo.toml, crates/operations/Cargo.toml, crates/render/Cargo.toml, crates/sketch/Cargo.toml, crates/topology/Cargo.toml, crates/wasm-macros/Cargo.toml, crates/wasm/Cargo.toml, xtask/Cargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Rust (statically typed)
51.8/55Manageable file sizes — 35/607 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes414,736
source_files_sampled607
oversized_source_files35
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 — examples
Inputs used
example_dirsexamples
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

31GitHub stars
2contributors
1,818commits, last 12 months
0days since last push
100releases
1bus factor
0open issues
crates.io, npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • crates package 'xtask' points at a different repository (https://github.com/arcboxlabs/xtask); excluded from ecosystem scoring
  • Could not fetch npm package '@brepkit/wasm' from its registry

More detail

Star and fork history 0 ★ / 5 ⇿
0Stars
5Forks
18Releases

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.

12345512026-032026-062026-09
Major 0Minor 1Patch 17
OpenSSF Scorecard 6.9 / 10
6.9aggregate

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-27 07:22 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests30 out of 30 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 0/30 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 15 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
9Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 9
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 83
RegistryPackageVersion constraintManifest
crates.ioanyhow1xtask/Cargo.toml
crates.ioclap4xtask/Cargo.toml
crates.ioserde_json1xtask/Cargo.toml
crates.iobrepkit-math—crates/algo/Cargo.toml
crates.iobrepkit-topology—crates/algo/Cargo.toml
crates.iolog—crates/algo/Cargo.toml
crates.iothiserror—crates/algo/Cargo.toml
crates.iobrepkit-math—crates/blend/Cargo.toml
crates.iobrepkit-topology—crates/blend/Cargo.toml
crates.iolog—crates/blend/Cargo.toml
crates.iothiserror—crates/blend/Cargo.toml
crates.iobrepkit-geometry—crates/check/Cargo.toml
crates.iobrepkit-math—crates/check/Cargo.toml
crates.iobrepkit-topology—crates/check/Cargo.toml
crates.iosmallvec—crates/check/Cargo.toml
crates.iothiserror—crates/check/Cargo.toml
crates.iobrepkit-math—crates/geometry/Cargo.toml
crates.iothiserror—crates/geometry/Cargo.toml
crates.iobitflags—crates/heal/Cargo.toml
crates.iobrepkit-geometry—crates/heal/Cargo.toml
crates.iobrepkit-math—crates/heal/Cargo.toml
crates.iobrepkit-topology—crates/heal/Cargo.toml
crates.iolog—crates/heal/Cargo.toml
crates.iothiserror—crates/heal/Cargo.toml
crates.iobrepkit-math—crates/io/Cargo.toml
crates.iobrepkit-operations—crates/io/Cargo.toml
crates.iobrepkit-topology—crates/io/Cargo.toml
crates.ioquick-xml—crates/io/Cargo.toml
crates.ioserde—crates/io/Cargo.toml
crates.ioserde_json—crates/io/Cargo.toml
crates.iothiserror—crates/io/Cargo.toml
crates.iozip—crates/io/Cargo.toml
crates.iolog—crates/math/Cargo.toml
crates.iorobust—crates/math/Cargo.toml
crates.ioserde—crates/math/Cargo.toml
crates.iothiserror—crates/math/Cargo.toml
crates.iobrepkit-geometry—crates/offset/Cargo.toml
crates.iobrepkit-math—crates/offset/Cargo.toml
crates.iobrepkit-topology—crates/offset/Cargo.toml
crates.iolog—crates/offset/Cargo.toml
crates.iothiserror—crates/offset/Cargo.toml
crates.iobrepkit-algo—crates/operations/Cargo.toml
crates.iobrepkit-blend—crates/operations/Cargo.toml
crates.iobrepkit-check—crates/operations/Cargo.toml
crates.iobrepkit-geometry—crates/operations/Cargo.toml
crates.iobrepkit-heal—crates/operations/Cargo.toml
crates.iobrepkit-math—crates/operations/Cargo.toml
crates.iobrepkit-offset—crates/operations/Cargo.toml
crates.iobrepkit-sketch—crates/operations/Cargo.toml
crates.iobrepkit-topology—crates/operations/Cargo.toml
crates.iolog—crates/operations/Cargo.toml
crates.iorayon—crates/operations/Cargo.toml
crates.iothiserror—crates/operations/Cargo.toml
crates.iobrepkit-math—crates/render/Cargo.toml
crates.iobrepkit-operations—crates/render/Cargo.toml
crates.iobrepkit-topology—crates/render/Cargo.toml
crates.iobytemuck1crates/render/Cargo.toml
crates.ioimage0.25crates/render/Cargo.toml
crates.iopollster1.0crates/render/Cargo.toml
crates.iothiserror—crates/render/Cargo.toml
crates.iowgpu30crates/render/Cargo.toml
crates.iolog—crates/render/Cargo.toml
crates.iowinit0.30crates/render/Cargo.toml
crates.iothiserror—crates/sketch/Cargo.toml
crates.iobrepkit-math—crates/topology/Cargo.toml
crates.iosmallvec—crates/topology/Cargo.toml
crates.iothiserror—crates/topology/Cargo.toml
crates.ioquote1crates/wasm-macros/Cargo.toml
crates.iosyn3crates/wasm-macros/Cargo.toml
crates.iobrepkit-algo—crates/wasm/Cargo.toml
crates.iobrepkit-check—crates/wasm/Cargo.toml
crates.iobrepkit-geometry—crates/wasm/Cargo.toml
crates.iobrepkit-heal—crates/wasm/Cargo.toml
crates.iobrepkit-io—crates/wasm/Cargo.toml
crates.iobrepkit-math—crates/wasm/Cargo.toml
crates.iobrepkit-operations—crates/wasm/Cargo.toml
crates.iobrepkit-topology—crates/wasm/Cargo.toml
crates.iolog—crates/wasm/Cargo.toml
crates.ioserde—crates/wasm/Cargo.toml
crates.ioserde_json—crates/wasm/Cargo.toml
crates.iothiserror—crates/wasm/Cargo.toml
crates.iotsify—crates/wasm/Cargo.toml
crates.iowasm-bindgen—crates/wasm/Cargo.toml
All dependencies 110

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

RegistryPackageVersionRelation
crates.ioanyhow—direct
crates.iobytemuck—direct
crates.ioclap—direct
crates.ioimage—direct
crates.iopollster—direct
crates.ioquote—direct
crates.ioserde_json—direct
crates.iosyn—direct
crates.iowgpu—direct
crates.iowinit—direct
crates.iotempfile—indirect
npm@babel/code-frame7.29.7indirect
npm@babel/helper-validator-identifier7.29.7indirect
npm@commitlint/cli21.2.2indirect
npm@commitlint/config-conventional21.2.2indirect
npm@commitlint/config-validator21.2.0indirect
npm@commitlint/ensure21.2.0indirect
npm@commitlint/execute-rule21.0.1indirect
npm@commitlint/format21.2.2indirect
npm@commitlint/is-ignored21.2.2indirect
npm@commitlint/lint21.2.2indirect
npm@commitlint/load21.2.2indirect
npm@commitlint/message21.2.0indirect
npm@commitlint/parse21.2.2indirect
npm@commitlint/read21.2.1indirect
npm@commitlint/resolve-extends21.2.2indirect
npm@commitlint/rules21.2.2indirect
npm@commitlint/to-lines21.0.1indirect
npm@commitlint/top-level21.2.0indirect
npm@commitlint/types21.2.0indirect
npm@conventional-changelog/git-client3.1.0indirect
npm@conventional-changelog/template1.3.0indirect
npm@simple-libs/child-process-utils2.0.0indirect
npm@simple-libs/stream-utils2.0.0indirect
npm@types/node26.2.0indirect
npm@typescript-eslint/eslint-plugin^8.0.0indirect
npm@typescript-eslint/parser^8.0.0indirect
npm@typescript/typescript-aix-ppc647.0.2indirect
npm@typescript/typescript-darwin-arm647.0.2indirect
npm@typescript/typescript-darwin-x647.0.2indirect
npm@typescript/typescript-freebsd-arm647.0.2indirect
npm@typescript/typescript-freebsd-x647.0.2indirect
npm@typescript/typescript-linux-arm7.0.2indirect
npm@typescript/typescript-linux-arm647.0.2indirect
npm@typescript/typescript-linux-loong647.0.2indirect
npm@typescript/typescript-linux-mips64el7.0.2indirect
npm@typescript/typescript-linux-ppc647.0.2indirect
npm@typescript/typescript-linux-riscv647.0.2indirect
npm@typescript/typescript-linux-s390x7.0.2indirect
npm@typescript/typescript-linux-x647.0.2indirect
npm@typescript/typescript-netbsd-arm647.0.2indirect
npm@typescript/typescript-netbsd-x647.0.2indirect
npm@typescript/typescript-openbsd-arm647.0.2indirect
npm@typescript/typescript-openbsd-x647.0.2indirect
npm@typescript/typescript-sunos-x647.0.2indirect
npm@typescript/typescript-win32-arm647.0.2indirect
npm@typescript/typescript-win32-x647.0.2indirect
npmajv8.20.0indirect
npmansi-regex6.2.2indirect
npmansi-styles6.2.3indirect
npmargparse2.0.1indirect
npmcallsites3.1.0indirect
npmcliui9.0.1indirect
npmconventional-changelog-angular9.3.0indirect
npmconventional-changelog-conventionalcommits10.2.1indirect
npmconventional-commits-parser7.0.1indirect
npmcosmiconfig9.0.2indirect
npmcosmiconfig-typescript-loader6.3.0indirect
npmemoji-regex10.6.0indirect
npmenv-paths2.2.1indirect
npmerror-ex1.3.4indirect
npmes-toolkit1.51.0indirect
npmescalade3.2.0indirect
npmeslint^9.0.0indirect
npmfast-deep-equal3.1.3indirect
npmfast-uri3.1.7indirect
npmget-caller-file2.0.5indirect
npmget-east-asian-width1.6.0indirect
npmglobal-directory5.0.0indirect
npmhusky9.1.7indirect
npmimport-fresh3.3.1indirect
npmini6.0.0indirect
npmis-arrayish0.2.1indirect
npmis-plain-obj4.1.0indirect
npmjiti2.6.1indirect
npmjs-tokens4.0.0indirect
npmjs-yaml4.3.2indirect
npmjson-parse-even-better-errors2.3.1indirect
npmjson-schema-traverse1.0.0indirect
npmlines-and-columns1.2.4indirect
npmmeow14.1.0indirect
npmparent-module1.0.1indirect
npmparse-json5.2.0indirect
npmpicocolors1.1.1indirect
npmprettier3.9.6indirect
npmrequire-from-string2.0.2indirect
npmresolve-from4.0.0indirect
npmresolve-from5.0.0indirect
npmsemver7.8.5indirect
npmstring-width7.2.0indirect
npmstrip-ansi7.2.0indirect
npmtinyexec1.2.4indirect
npmtypescript7.0.2indirect
npmtypescript^5.7.0indirect
npmundici-types8.3.0indirect
npmvitest^4.1.8indirect
npmwrap-ansi9.0.2indirect
npmy18n5.0.8indirect
npmyargs18.0.0indirect
npmyargs-parser22.0.0indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 94 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 16 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

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 — crates.io.