Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-13 19:29 UTC

puffinsoft / jscanify

The Javascript document scanning library.

JavaScriptMIT★ 1,773 stars⑂ 81 forkssince Apr 2023View on GitHub ↗

#js #javascript #document-scanner #nodejs

puffinsoft/jscanify holds a health index of 48 out of 100, placing it in the Weak band. It scores highest on Community & Adoption (68/100) and lowest on AI Readiness (26/100). It was last updated 55 days ago. A single contributor accounts for most of its recent work.

overall / 100

Weak

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.

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)

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

Ownership

puffinsoftOrganization

14 followers11 public repossince Jul 2024

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

Package ecosystems

Registry	Package	Version	Downloads / mo	Versions	Last publish	Tags
npm	jscanify	1.4.3	78,614	12	55 days ago	js scanner document-scanner

Metrics by category

Vitality

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

38Weak · 21% of overall

Development activity

29At Risk

How it's scored

18/36	Push recency — last push 55 days ago
2.1/36	Commit cadence — 3/52 weeks with commits
8.6/18	Commit volume — 8 commits in the last year
0/10	OpenSSF Scorecard: Maintained — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0

Inputs used

commits_last_year	8
human_commit_share	1
days_since_last_push	55
active_weeks_last_year	3

Release discipline

52Moderate

How it's scored

27/27	Ships releases — 5 releases published
7.2/36	Release recency — latest release 572 days ago
12.6/27	Release cadence — a release every ~168.9 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	5
latest_release_tag	v1.4.0
releases_from_tags	no
days_since_latest_release	572
mean_days_between_releases	168.9

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?

68Good · 17% of overall

Popularity & adoption

75Good

How it's scored

52.7/60	Stars — 1,773 stars
15.9/25	Forks — 81 forks
6.4/15	Watchers — 15 watchers

Inputs used

forks	81
stars	1,773
watchers	15
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

50Moderate

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (MIT)
0/18	CONTRIBUTING guide
0/13.5	Code of conduct
0/7.2	Issue template
0/6.3	PR template

Inputs used

has_readme	yes
has_license	yes
readme_badges	4
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	badgen.net, shields.io
has_pull_request_template	no

Ecosystem adoption (downloads)

82Excellent

How it's scored

65.3/80	Monthly downloads — 78,614 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	jscanify
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	78,614
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?

56Moderate · 23% of overall

Maintainer resilience (bus factor)

17Critical

How it's scored

9/54	Bus factor — 1 contributor(s) cover half of all commits
0.5/22.5	Commit distribution — top contributor authored 98% of commits
4.1/13.5	Contributor breadth — 3 contributors
3/10	OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3

Inputs used

bus_factor	1
contributors_sampled	3
top_contributor_share	0.978

Issue & PR responsiveness

74Good

How it's scored

42/42	Issue resolution — 100% of issues closed
22.5/30	PR acceptance — 3/4 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15	OpenSSF Scorecard: Code-Review — Found 2/30 approved changesets -- score normalized to 0

Inputs used

merged_prs	3
open_issues	0
closed_issues	31
prs_merged_7d	0
prs_decided_7d	0
prs_merged_30d	0
prs_decided_30d	0
issue_closed_ratio	1
closed_unmerged_prs	1
first_time_authors_30d	0
first_time_prs_merged_30d	0
first_time_prs_decided_30d	0

Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

51Moderate

How it's scored

30/30	Ownership backing — organization-owned
0/20	Verified domain
8.5/25	Owner reach — 14 followers of puffinsoft
12.2/25	Track record — 11 public repos, account ~2 yr old

Inputs used

followers	14
owner_type	Organization
is_verified	no
owner_login	puffinsoft
public_repos	11
account_age_days	798

Package maintenance

100Exceptional

How it's scored

25/25	Published & resolvable — 1 package(s) on npm
35/35	Publish recency — latest publish 55 days ago
20/20	Version history — 12 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	jscanify
ecosystems	npm
any_deprecated	no
min_days_since_publish	55

Engineering Quality

Are baseline engineering and documentation practices in place?

54Moderate · 19% of overall

Engineering practices

24At Risk

How it's scored

0/24	CI workflows
24/24	Tests present
0/16	Linter config
0/9.6	Pre-commit hooks
0/6.4	.editorconfig
0/20	OpenSSF Scorecard: CI-Tests — 0 out of 2 merged PRs checked by a CI test -- score normalized to 0

Inputs used

has_ci	no
has_tests	yes
has_editorconfig	no
has_linter_config	no
has_precommit_config	no

Documentation

100Exceptional

How it's scored

30/30	README
25/25	Documentation directory
15/15	Documentation / homepage site — https://colonelparrot.github.io/jscanify/
10/10	Repository description
10/10	Topics — 4 topics
10/10	Wiki

Inputs used

topics	js, javascript, document-scanner, nodejs
has_wiki	yes
homepage	https://colonelparrot.github.io/jscanify/
docs_site	https://colonelparrot.github.io/jscanify/
has_readme	yes
has_docs_dir	yes
has_description	yes

Security

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

34At Risk · 16% of overall

Security posture

17Critical

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
0/7.5	Branch-Protection — branch protection not enabled on development/release branches
0/2.5	CI-Tests — 0 out of 2 merged PRs checked by a CI test -- score normalized to 0
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5	Code-Review — Found 2/30 approved changesets -- score normalized to 0
0.8/2.5	Contributors — project has 1 contributing companies or organizations -- score normalized to 3
0/10	Dangerous-Workflow — no data
0/7.5	Dependency-Update-Tool — no update tool detected
0/5	Fuzzing — project is not fuzzed
2.5/2.5	License — license file detected
0/7.5	Maintained — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5	Packaging — no data
0/5	Pinned-Dependencies — no data
0/5	SAST — SAST tool is not run on all commits -- score normalized to 0
0/5	Security-Policy — security policy file not detected
0/7.5	Signed-Releases — no data
0/7.5	Token-Permissions — no data
0.8/7.5	Vulnerabilities — 9 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	13
scorecard_version	v5.5.0
checks_inconclusive	5
scorecard_aggregate	1.6

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/35	Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25	Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40	No advisories left outstanding — no advisory carries a publication date

Inputs used

source	osv
advisories	0
affected_packages	0
assessed_packages	76
unassessed_packages	0
affected_by_severity	none
direct_affected_packages	0

Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:jscanify@1.4.3 runtime dependency closure — what installing the published package pulls in — 76 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.

26At Risk · 4% of overall

Agent context & guidance

4Critical

How it's scored

0/45	Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15	Machine-readable docs (llms.txt)
4.2/40	Legible commit history — 7 of 89 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	no
llms_txt_url	—
legible_history_share	0.079
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

36Weak

How it's scored

0/18	One-command bootstrap
22/22	Automated tests
0/11	Lint / format config
0/11	Static type checking
10/10	Reproducible environment — lockfile
0/10	Demonstrated agent practice — no agent-authored commits among the last 89
0/8	Automated maintenance — no automated dependency updates observed
0/10	OpenSSF Scorecard: Pinned-Dependencies — no data

Inputs used

has_nix	no
has_tests	yes
lockfiles	package-lock.json
has_dockerfile	no
typed_language	no
bootstrap_files	—
has_devcontainer	no
has_linter_config	no
typecheck_configs	—
agent_commit_share	0
toolchain_manifests	—
dependency_bot_commit_share	0

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.

Code legibility for models

44Weak

How it's scored

0/45	Type-checkable code — JavaScript without a type-check config
44/55	Manageable file sizes — 1/5 source files over 60KB

Inputs used

primary_language	JavaScript
largest_source_bytes	8,980,560
source_files_sampled	5
oversized_source_files	1

Key facts

1,773GitHub stars

3contributors

8commits, last 12 months

55days since last push

5releases

1bus factor

0open issues

npmpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 81 ⇿

0Stars

81Forks

5Releases

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.

Major 1Minor 4Patch 0

Each point covers 4 days.

OpenSSF Scorecard 1.6 / 10

1.6aggregate

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-13 19:28 UTC

10	Binary-Artifacts	no binaries found in the repo
0	Branch-Protection	branch protection not enabled on development/release branches
0	CI-Tests	0 out of 2 merged PRs checked by a CI test -- score normalized to 0
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
0	Code-Review	Found 2/30 approved changesets -- score normalized to 0
3	Contributors	project has 1 contributing companies or organizations -- score normalized to 3
n/a	Dangerous-Workflow	no workflows found
0	Dependency-Update-Tool	no update tool detected
0	Fuzzing	project is not fuzzed
10	License	license file detected
0	Maintained	1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/a	Packaging	packaging workflow not detected
n/a	Pinned-Dependencies	no dependencies found
0	SAST	SAST tool is not run on all commits -- score normalized to 0
0	Security-Policy	security policy file not detected
n/a	Signed-Releases	no releases found
n/a	Token-Permissions	No tokens found
1	Vulnerabilities	9 existing vulnerabilities detected

Direct dependencies 2

Registry	Package	Version constraint	Manifest
npm	canvas	`^3.2.3`	package.json
npm	jsdom	`^29.1.1`	package.json

All dependencies 151

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

Registry	Package	Version	Relation
npm	canvas	`3.2.3`	direct
npm	jsdom	`29.1.1`	direct
npm	@asamuzakjp/css-color	`5.1.11`	indirect
npm	@asamuzakjp/dom-selector	`7.1.1`	indirect
npm	@asamuzakjp/generational-cache	`1.0.1`	indirect
npm	@asamuzakjp/nwsapi	`2.3.9`	indirect
npm	@bramus/specificity	`2.4.2`	indirect
npm	@csstools/color-helpers	`6.1.0`	indirect
npm	@csstools/css-calc	`3.2.1`	indirect
npm	@csstools/css-color-parser	`4.1.9`	indirect
npm	@csstools/css-parser-algorithms	`4.0.0`	indirect
npm	@csstools/css-syntax-patches-for-csstree	`1.1.6`	indirect
npm	@csstools/css-tokenizer	`4.0.0`	indirect
npm	@exodus/bytes	`1.15.1`	indirect
npm	@isaacs/cliui	`8.0.2`	indirect
npm	@pkgjs/parseargs	`0.11.0`	indirect
npm	ansi-regex	`5.0.1`	indirect
npm	ansi-regex	`6.2.2`	indirect
npm	ansi-styles	`4.3.0`	indirect
npm	ansi-styles	`6.2.3`	indirect
npm	argparse	`2.0.1`	indirect
npm	balanced-match	`1.0.2`	indirect
npm	base64-js	`1.5.1`	indirect
npm	bidi-js	`1.0.3`	indirect
npm	bl	`4.1.0`	indirect
npm	brace-expansion	`2.1.2`	indirect
npm	browser-stdout	`1.3.1`	indirect
npm	buffer	`5.7.1`	indirect
npm	camelcase	`6.3.0`	indirect
npm	chalk	`4.1.2`	indirect
npm	chokidar	`4.0.3`	indirect
npm	chownr	`1.1.4`	indirect
npm	cliui	`8.0.1`	indirect
npm	color-convert	`2.0.1`	indirect
npm	color-name	`1.1.4`	indirect
npm	cross-spawn	`7.0.6`	indirect
npm	css-tree	`3.2.1`	indirect
npm	data-urls	`7.0.0`	indirect
npm	debug	`4.4.3`	indirect
npm	decamelize	`4.0.0`	indirect
npm	decimal.js	`10.6.0`	indirect
npm	decompress-response	`6.0.0`	indirect
npm	deep-extend	`0.6.0`	indirect
npm	detect-libc	`2.1.2`	indirect
npm	diff	`8.0.3`	indirect
npm	eastasianwidth	`0.2.0`	indirect
npm	emoji-regex	`8.0.0`	indirect
npm	emoji-regex	`9.2.2`	indirect
npm	end-of-stream	`1.4.5`	indirect
npm	entities	`8.0.0`	indirect
npm	escalade	`3.2.0`	indirect
npm	escape-string-regexp	`4.0.0`	indirect
npm	expand-template	`2.0.3`	indirect
npm	find-up	`5.0.0`	indirect
npm	flat	`5.0.2`	indirect
npm	foreground-child	`3.3.1`	indirect
npm	fs-constants	`1.0.0`	indirect
npm	get-caller-file	`2.0.5`	indirect
npm	github-from-package	`0.0.0`	indirect
npm	glob	`10.5.0`	indirect
npm	has-flag	`4.0.0`	indirect
npm	he	`1.2.0`	indirect
npm	html-encoding-sniffer	`6.0.0`	indirect
npm	ieee754	`1.2.1`	indirect
npm	inherits	`2.0.4`	indirect
npm	ini	`1.3.8`	indirect
npm	is-fullwidth-code-point	`3.0.0`	indirect
npm	is-path-inside	`3.0.3`	indirect
npm	is-plain-obj	`2.1.0`	indirect
npm	is-potential-custom-element-name	`1.0.1`	indirect
npm	is-unicode-supported	`0.1.0`	indirect
npm	isexe	`2.0.0`	indirect
npm	jackspeak	`3.4.3`	indirect
npm	js-yaml	`4.3.0`	indirect
npm	locate-path	`6.0.0`	indirect
npm	log-symbols	`4.1.0`	indirect
npm	lru-cache	`10.4.3`	indirect
npm	lru-cache	`11.5.2`	indirect
npm	mdn-data	`2.27.1`	indirect
npm	mimic-response	`3.1.0`	indirect
npm	minimatch	`9.0.9`	indirect
npm	minimist	`1.2.8`	indirect
npm	minipass	`7.1.3`	indirect
npm	mkdirp-classic	`0.5.3`	indirect
npm	mocha	`11.7.6`	indirect
npm	ms	`2.1.3`	indirect
npm	napi-build-utils	`2.0.0`	indirect
npm	node-abi	`3.88.0`	indirect
npm	node-addon-api	`7.1.1`	indirect
npm	once	`1.4.0`	indirect
npm	p-limit	`3.1.0`	indirect
npm	p-locate	`5.0.0`	indirect
npm	package-json-from-dist	`1.0.1`	indirect
npm	parse5	`8.0.1`	indirect
npm	path-exists	`4.0.0`	indirect
npm	path-key	`3.1.1`	indirect
npm	path-scurry	`1.11.1`	indirect
npm	picocolors	`1.1.1`	indirect
npm	prebuild-install	`7.1.3`	indirect
npm	pump	`3.0.4`	indirect
npm	punycode	`2.3.1`	indirect
npm	rc	`1.2.8`	indirect
npm	readable-stream	`3.6.2`	indirect
npm	readdirp	`4.1.2`	indirect
npm	require-directory	`2.1.1`	indirect
npm	require-from-string	`2.0.2`	indirect
npm	safe-buffer	`5.2.1`	indirect
npm	saxes	`6.0.0`	indirect
npm	semver	`7.7.4`	indirect
npm	serialize-javascript	`7.0.5`	indirect
npm	shebang-command	`2.0.0`	indirect
npm	shebang-regex	`3.0.0`	indirect
npm	signal-exit	`4.1.0`	indirect
npm	simple-concat	`1.0.1`	indirect
npm	simple-get	`4.0.1`	indirect
npm	source-map-js	`1.2.1`	indirect
npm	string-width	`4.2.3`	indirect
npm	string-width	`5.1.2`	indirect
npm	string_decoder	`1.3.0`	indirect
npm	strip-ansi	`6.0.1`	indirect
npm	strip-ansi	`7.2.0`	indirect
npm	strip-json-comments	`2.0.1`	indirect
npm	strip-json-comments	`3.1.1`	indirect
npm	supports-color	`7.2.0`	indirect
npm	supports-color	`8.1.1`	indirect
npm	symbol-tree	`3.2.4`	indirect
npm	tar-fs	`2.1.4`	indirect
npm	tar-stream	`2.2.0`	indirect
npm	tldts	`7.4.9`	indirect
npm	tldts-core	`7.4.9`	indirect
npm	tough-cookie	`6.0.2`	indirect
npm	tr46	`6.0.0`	indirect
npm	tunnel-agent	`0.6.0`	indirect
npm	undici	`7.28.0`	indirect
npm	util-deprecate	`1.0.2`	indirect
npm	w3c-xmlserializer	`5.0.0`	indirect
npm	webidl-conversions	`8.0.1`	indirect
npm	whatwg-mimetype	`5.0.0`	indirect
npm	whatwg-url	`16.0.1`	indirect
npm	which	`2.0.2`	indirect
npm	workerpool	`9.3.4`	indirect
npm	wrap-ansi	`7.0.0`	indirect
npm	wrap-ansi	`8.1.0`	indirect
npm	wrappy	`1.0.2`	indirect
npm	xml-name-validator	`5.0.0`	indirect
npm	xmlchars	`2.2.0`	indirect
npm	y18n	`5.0.8`	indirect
npm	yargs	`17.7.3`	indirect
npm	yargs-parser	`21.1.1`	indirect
npm	yargs-unparser	`2.0.0`	indirect
npm	yocto-queue	`0.1.0`	indirect

Dependency advisories 0

Installing npm:jscanify@1.4.3 pulls in 76 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.

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.

Software health index

Score profile

Ownership

Package ecosystems

Metrics by category

Key facts

Data collection warnings

More detail

Feedback

Related records