Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-04 22:12 UTC

JunHwan-Kwon / deepbom

Local static analysis and evidence generation for deployed AI model artifacts

JavaScript · RustApache-2.0★ 2 stars⑂ 0 forkssince Aug 2026View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

JunHwan-Kwon/deepbom holds a health index of 53 out of 100, placing it in the Moderate band. It scores highest on Vitality (74/100) and lowest on Community & Adoption (39/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

JunHwanKwonPersonal account
2 followers2 public repossince Apr 2026

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?

74Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
1.4/36Commit cadence2/52 weeks with commits
14/18Commit volume35 commits in the last year
0/10OpenSSF Scorecard: Maintainedno data
Inputs used
commits_last_year35
human_commit_share1
days_since_last_push0
active_weeks_last_year2

Release discipline

100Exceptional
How it's scored
27/27Ships releases11 releases published
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count11
latest_release_tagchannels-v1.96.8
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases1

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

39Weak · 17% of overall
How it's scored
0/60Stars2 stars
0/25Forks0 forks
0/15Watchers0 watchers
Inputs used
forks0
stars2
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
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
46.5/80Monthly downloads3,094 downloads/month across crates, npm, pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesdeepbom, deepbom, deepbom
dependents
ecosystemscrates, npm, pypi
total_downloads124
monthly_downloads3,094
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?

42Weak · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
5.9/22.5Commit distributiontop contributor authored 74% of commits
2.7/13.5Contributor breadth2 contributors
0/10OpenSSF Scorecard: Contributorsno data
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.739
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
3.4/25Owner reach2 followers of JunHwan-Kwon
4.2/25Track record2 public repos, account ~0 yr old
Inputs used
followers2
owner_typeUser
is_verified
owner_loginJunHwan-Kwon
public_repos2
account_age_days136
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable3 package(s) on crates, npm, pypi
35/35Publish recencylatest publish 0 days ago
20/20Version history14 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesdeepbom, deepbom, deepbom
ecosystemscrates, npm, pypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

50Moderate · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

80Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://deepbom.org
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepagehttps://deepbom.org
docs_sitehttps://deepbom.org
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

55Moderate · 16% of overall
How it's scored
30/30Security policy (SECURITY.md)
0/25Dependabot config
25/25Dependency lockfilesCargo.lock, package-lock.json
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilesCargo.lock, package-lock.json
manifestsCargo.toml, package.json, pkg/package.json, requirements-onnx-corpus.txt
has_codeql_workflowno
has_security_policyyes
has_dependabot_configno

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.

45Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history45 of 46 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.978
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapCargo.toml, channels/cargo/Cargo.toml, native/runtime_collector/Cargo.toml (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentDockerfile, lockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 46
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsno
lockfilesCargo.lock, package-lock.json
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsCargo.toml, channels/cargo/Cargo.toml, native/runtime_collector/Cargo.toml, native/runtime_probe/Cargo.toml
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
51.2/55Manageable file sizes54/779 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes404,363
source_files_sampled779
oversized_source_files54
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 examplesexamples, samples
Inputs used
example_dirsexamples, samples
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

2GitHub stars
2contributors
35commits, last 12 months
0days since last push
11releases
1bus factor
0open issues
crates.io, npm, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch crates package 'tflite_wasm_audit' from its registry
  • Could not fetch npm package 'tflite_wasm_audit' from its registry
  • Could not fetch crates package 'deepbom-runtime-contract-probe' from its registry
  • Could not fetch crates package 'deepbom-runtime-collector' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • deps.dev does not index crates:deepbom@1.96.8; advisories assessed against the repository dependency graph instead
  • OpenSSF Scorecard did not return a usable result (killed by SIGKILL — most likely the container's memory limit; 2026/09/04 22:11:39 Warning: PATs stored in env variables GITHUB_AUTH_TOKEN and GITHUB_TOKEN differ. Scorecard will use the former.); skipping Scorecard checks

More detail

Direct dependencies 20
RegistryPackageVersion constraintManifest
crates.ioserde1Cargo.toml
crates.ioserde_json1Cargo.toml
crates.ioserde-wasm-bindgen0.6Cargo.toml
crates.iosha20.10Cargo.toml
crates.iowasm-bindgen0.2Cargo.toml
crates.iojs-sys0.3Cargo.toml
crates.iominiz_oxide0.9Cargo.toml
npm@litertjs/core^2.5.2package.json
npmjsonpath-rfc95351.3.0package.json
npmonnxruntime-web^1.26.0package.json
crates.ioserde1.0.228channels/cargo/Cargo.toml
crates.ioserde_json1.0.149channels/cargo/Cargo.toml
crates.iosha20.10.9channels/cargo/Cargo.toml
crates.ioureq=3.1.4channels/cargo/Cargo.toml
crates.ioserde1native/runtime_collector/Cargo.toml
crates.ioserde_json1native/runtime_collector/Cargo.toml
crates.iosha20.10native/runtime_collector/Cargo.toml
crates.ioserde1native/runtime_probe/Cargo.toml
crates.ioserde_json1native/runtime_probe/Cargo.toml
crates.iosha20.10native/runtime_probe/Cargo.toml
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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 statisticscrates.io, PyPI, npm.