Public record
Software health reportschema 0.14.0 · metrics 2.10.0 · 2026-07-18 23:14 UTC

microlinkhq / browserless

The headless Chrome/Chromium driver on top of Puppeteer. Take screenshots, generate PDFs, extract text and HTML with a production-ready API.

JavaScriptMIT★ 1,826 stars⑂ 92 forkssince Sep 2017View on GitHub ↗

microlinkhq/browserless holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Vitality (93/100) and lowest on AI Readiness (36/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

microlink.ioOrganization
363 followers62 public repossince Jun 2017

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

Metrics by category

Vitality

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

93Exceptional · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
24.9/36Commit cadence36/52 weeks with commits
18/18Commit volume297 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year297
human_commit_share
days_since_last_push0
active_weeks_last_year36

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~2.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv13.6.5
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases2.5
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?

67Good · 17% of overall
How it's scored
52.9/60Stars1,826 stars
16.3/25Forks92 forks
5/15Watchers9 watchers
Inputs used
forks92
stars1,826
watchers9
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
7.2/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateyes
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

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 factor1 contributor(s) cover half of all commits
2.5/22.5Commit distributiontop contributor authored 89% of commits
13.5/13.5Contributor breadth21 contributors
10/10OpenSSF Scorecard: Contributorsproject has 6 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled21
top_contributor_share0.891
How it's scored
39.7/42Issue resolution95% of issues closed
21.3/30PR acceptance542/765 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/16 approved changesets -- score normalized to 0
Inputs used
merged_prs542
open_issues4
closed_issues70
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.946
closed_unmerged_prs223
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
18.4/25Owner reach363 followers of microlinkhq
25/25Track record62 public repos, account ~9 yr old
Inputs used
followers363
owner_typeOrganization
is_verified
owner_loginmicrolinkhq
public_repos62
account_age_days3,305
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
6/20OpenSSF Scorecard: CI-Tests8 out of 22 merged PRs checked by a CI test -- score normalized to 3
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://browserless.js.org
10/10Repository description
10/10Topics8 topics
10/10Wiki
Inputs used
topicsautomation, browser-automation, chromium, lighthouse, pdf-generation, screenshot, web-crawler, web-scraping
has_wikiyes
homepagehttps://browserless.js.org
docs_sitehttps://browserless.js.org
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

39Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0.8/2.5CI-Tests8 out of 22 merged PRs checked by a CI test -- score normalized to 3
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/16 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 6 contributing companies or organizations
0/10Dangerous-Workflowdangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.9
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

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.

36Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
55/55Manageable file sizes0/110 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes28,048
source_files_sampled110
oversized_source_files0
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
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

1,826GitHub stars
21contributors
297commits, last 12 months
0days since last push
100releases
1bus factor
4open issues
npmpackage ecosystems

More detail

OpenSSF Scorecard 3.9 / 10
3.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-07-18 23:14 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
3CI-Tests8 out of 22 merged PRs checked by a CI test -- score normalized to 3
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/16 approved changesets -- score normalized to 0
10Contributorsproject has 6 contributing companies or organizations
0Dangerous-Workflowdangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not 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
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 96

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

RegistryPackageVersionRelation
npm@cloudflare/puppeteer~1.1.0indirect
npm@commitlint/clilatestindirect
npm@commitlint/config-conventionallatestindirect
npm@duckduckgo/autoconsent~16.11.0indirect
npm@ghostery/adblocker-puppeteer~2.18.0indirect
npm@kikobeats/content-type~1.0.4indirect
npm@kikobeats/time-spanlatestindirect
npm@kikobeats/time-span~1.0.12indirect
npm@lerna-lite/clilatestindirect
npm@lerna-lite/publishlatestindirect
npm@skyra/gifenclatestindirect
npmacorn~8.17.0indirect
npmacorn-walk~8.3.5indirect
npmasciichartlatestindirect
npmasync-listenlatestindirect
npmautomad-prism-themes~0.3.7indirect
npmava5indirect
npmbeauty-error~1.2.22indirect
npmbrowser-synclatestindirect
npmc8latestindirect
npmcanvaslatestindirect
npmconcurrentlylatestindirect
npmcssnanolatestindirect
npmcssnano-preset-advancedlatestindirect
npmdark-mode~3.0.0indirect
npmdebug-logfmtlatestindirect
npmdebug-logfmt~1.4.10indirect
npmdidyoumean3~1.2.5indirect
npmdset~3.1.4indirect
npmensure-error~3.0.1indirect
npmfinepacklatestindirect
npmfs-extralatestindirect
npmgit-authors-clilatestindirect
npmgithub-generate-releaselatestindirect
npmgot~11.8.6indirect
npmgulp4indirect
npmgulp-concatlatestindirect
npmgulp-postcsslatestindirect
npmgulp-uglifylatestindirect
npmimg-diff-jslatestindirect
npmis-html-content~1.0.0indirect
npmis-url-http~2.3.13indirect
npmisolated-function~0.1.63indirect
npmkill-process-group~1.0.13indirect
npmlighthouse~13.4.0indirect
npmlodashlatestindirect
npmlodash~4.18.1indirect
npmmap-values-deep~1.0.2indirect
npmmeasuredlatestindirect
npmmemoize-one~6.0.0indirect
npmmeow9indirect
npmmime~3.0.0indirect
npmmri~1.2.0indirect
npmnano-stagedlatestindirect
npmnanobenchlatestindirect
npmnanospinner~1.2.2indirect
npmnestie~1.0.3indirect
npmnpm-check-updateslatestindirect
npmnull-prototype-object~1.2.6indirect
npmp-all3indirect
npmp-reflect~2.1.0indirect
npmp-retry~4.6.1indirect
npmp-timeout~4.1.0indirect
npmpdf-parselatestindirect
npmpercentilelatestindirect
npmpostcsslatestindirect
npmpostcss-focuslatestindirect
npmpretty-bytes~5.6.0indirect
npmpretty-ms7indirect
npmpretty-ms~7.0.1indirect
npmprism-themes~1.9.0indirect
npmprocess-statslatestindirect
npmprocess-stats~3.7.16indirect
npmps-list7indirect
npmpuppeteer25indirect
npmrequire-one-of~1.0.24indirect
npmrestore-cursor~3.1.0indirect
npmserialize-error~8.1.0indirect
npmshallow-equal~3.1.0indirect
npmsharplatestindirect
npmsharp~0.35.1indirect
npmsieve-of-eratostheneslatestindirect
npmsignal-exitlatestindirect
npmsignal-exit~4.1.0indirect
npmsimple-git-hookslatestindirect
npmstandardlatestindirect
npmsuperlock~1.3.1indirect
npmsvg-gradient~1.0.4indirect
npmtempermentlatestindirect
npmterm-imglatestindirect
npmterm-img~5.0.0indirect
npmtinyspawnlatestindirect
npmtough-cookie~6.0.1indirect
npmunique-random-array~3.0.0indirect
npmwhoops~5.1.1indirect
npmws~8.21.0indirect
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.14.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics.