Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-12 10:14 UTC

Dynamsoft / barcode-reader-javascript

Dynamsoft Barcode Reader JavaScript SDK for package managers. PDF417, QR Code, DataMatrix, MaxiCode and more are supported.

Custom license★ 183 stars⑂ 103 forkssince Aug 2018View on GitHub ↗

Dynamsoft/barcode-reader-javascript holds a health index of 57 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (76/100) and lowest on AI Readiness (14/100). It was last updated 35 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

DynamsoftOrganization · verified domain
76 followers87 public repossince Oct 2013

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

Package ecosystems

Metrics by category

Vitality

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

63Moderate · 21% of overall
How it's scored
18/36Push recency — last push 35 days ago
4.8/36Commit cadence — 7/52 weeks with commits
13.1/18Commit volume — 28 commits in the last year
8/10OpenSSF Scorecard: Maintained — 10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
Inputs used
commits_last_year28
human_commit_share1
days_since_last_push35
active_weeks_last_year7
How it's scored
27/27Ships releases — 42 releases published
36/36Release recency — latest release 35 days ago
19.8/27Release cadence — a release every ~68 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count42
latest_release_tagv11.6.32
releases_from_tagsno
days_since_latest_release35
mean_days_between_releases68
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?

57Moderate · 17% of overall
How it's scored
36.7/60Stars — 183 stars
16.7/25Forks — 103 forks
5.6/15Watchers — 11 watchers
Inputs used
forks103
stars183
watchers11
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
58.2/80Monthly downloads — 23,318 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesdynamsoft-barcode-reader-bundle
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads23,318
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?

76Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
13/22.5Commit distribution — top contributor authored 42% of commits
8.1/13.5Contributor breadth — 6 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor2
contributors_sampled6
top_contributor_share0.423
How it's scored
31.2/42Issue resolution — 74% of issues closed
28/30PR acceptance — 125/134 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-Review — Found 7/18 approved changesets -- score normalized to 3
Inputs used
merged_prs125
open_issues8
closed_issues23
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.742
closed_unmerged_prs9
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
20/20Verified domain
13.6/25Owner reach — 76 followers of Dynamsoft
25/25Track record — 87 public repos, account ~12 yr old
Inputs used
followers76
owner_typeOrganization
is_verifiedyes
owner_loginDynamsoft
public_repos87
account_age_days4,729

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 37 days ago
20/20Version history — 67 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesdynamsoft-barcode-reader-bundle
ecosystemsnpm
any_deprecatedno
min_days_since_publish37

Engineering Quality

Are baseline engineering and documentation practices in place?

31At Risk · 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-Tests — 0 out of 7 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
15/15Documentation / homepage site — https://www.dynamsoft.com/barcode-reader/sdk-javascript/
10/10Repository description
10/10Topics — 16 topics
10/10Wiki
Inputs used
topicsjavascript-barcode, javascript-qrcode, barcode-reader, web, javascript, npm-package, barcode, html5-barcode, web-barcode, pdf417, qrcode, aztec-code, webassembly, sdk, linear-barcode, 1d-barcode
has_wikiyes
homepagehttps://www.dynamsoft.com/barcode-reader/sdk-javascript/
docs_sitehttps://www.dynamsoft.com/barcode-reader/sdk-javascript/
has_readmeyes
has_docs_dirno
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
3.8/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — no data
0/2.5CI-Tests — 0 out of 7 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-Review — Found 7/18 approved changesets -- score normalized to 3
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
6/7.5Maintained — 10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
0/5Packaging — no data
0/5Pinned-Dependencies — no data
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
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate3.7
Excluded from scoring (no data or not applicable): Branch-Protection, 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 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
advisories3
affected_packages2
assessed_packages12
unassessed_packages15
affected_by_severitycritical 1, high 1
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 12 resolved dependencies against OSV. 15 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.

14Critical · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://www.dynamsoft.com/llms.txt)
17.1/40Legible commit history — 32 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://www.dynamsoft.com/llms.txt
legible_history_share0.32
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.

Key facts

183GitHub stars
6contributors
28commits, last 12 months
35days since last push
42releases
2bus factor
8open issues
npmpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 103 ⇿
0Stars
103Forks
38Releases

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.

02040608010012010132018-122022-072026-03
Major 1Minor 2Patch 32

Each point covers 7 days.

OpenSSF Scorecard 3.7 / 10
3.7aggregate

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-10-12 10:14 UTC

5Binary-Artifactsbinaries present in source code
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
0CI-Tests0 out of 7 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 7/18 approved changesets -- score normalized to 3
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense 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
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 27

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

RegistryPackageVersionRelation
npm@babel/core^7.24.0indirect
npm@babel/preset-env^7.24.0indirect
npm@dynamsoft/dm-camera5.0.0-dev-20260904150200indirect
npm@dynamsoft/dynamsoft-barcode-reader11.6.30-dev-20260903131317indirect
npm@dynamsoft/dynamsoft-capture-vision-router3.6.30-dev-20260903131250indirect
npm@dynamsoft/dynamsoft-code-parser3.6.30-dev-20260903131344indirect
npm@dynamsoft/dynamsoft-core4.6.30-dev-20260903131243indirect
npm@dynamsoft/dynamsoft-image-processing3.6.30-dev-20260903131402indirect
npm@dynamsoft/dynamsoft-license4.6.30-dev-20260903131259indirect
npm@dynamsoft/dynamsoft-utility2.6.30-dev-20260903152426indirect
npm@dynamsoft/rd2-scripts0.1.56indirect
npm@rollup/plugin-babel^6.0.4indirect
npm@rollup/plugin-node-resolve^15.2.3indirect
npm@rollup/plugin-replace^5.0.5indirect
npm@rollup/plugin-terser^0.4.4indirect
npm@rollup/plugin-typescript^12indirect
npm@scannerproxy/curscript-path^2.0.6indirect
npm@scannerproxy/dlsjs3.0.43indirect
npm@types/node^25.9.1indirect
npmmutable-promise^1.1.15indirect
npmrollup^3.29.3indirect
npmrollup-plugin-dts^6.4.1indirect
npmterser^5.43.0indirect
npmtslib^2.6.2indirect
npmtypescript^6indirect
NuGetlog4net2.0.8indirect
NuGetNewtonsoft.Json12.0.2indirect
Dependency advisories 2

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

PackageVersionRelationSeverityAdvisoriesFixed in
log4net2.0.8indirectcritical23.3.0
Newtonsoft.Json12.0.2indirecthigh113.0.1

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.