Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-21 13:17 UTC

hyperbrowserai / python-sdk

PythonMIT★ 23 stars⑂ 5 forkssince Nov 2024View on GitHub ↗

hyperbrowserai/python-sdk holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Vitality (98/100) and lowest on Community & Adoption (54/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

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

Ownership

HyperbrowserOrganization
415 followers22 public repossince Nov 2024

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIhyperbrowser1.15.6442,4321651 day ago

Metrics by category

Vitality

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

98Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
31.8/36Commit cadence — 46/52 weeks with commits
18/18Commit volume — 137 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year137
human_commit_share1
days_since_last_push1
active_weeks_last_year46

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 62 releases published
36/36Release recency — latest release 1 days ago
27/27Release cadence — a release every ~3.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count62
latest_release_tagv1.15.6
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases3.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?

54Moderate · 17% of overall
How it's scored
21.8/60Stars — 23 stars
5/25Forks — 5 forks
0/15Watchers — 1 watchers
Inputs used
forks5
stars23
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateyes
How it's scored
75.3/80Monthly downloads — 442,432 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageshyperbrowser
dependents—
ecosystemspypi
total_downloads—
monthly_downloads442,432
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?

69Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
9.5/22.5Commit distribution — top contributor authored 58% 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_factor1
contributors_sampled6
top_contributor_share0.578
How it's scored
42/42Issue resolution — 100% of issues closed
28.6/30PR acceptance — 142/149 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
12/15OpenSSF Scorecard: Code-Review — Found 25/30 approved changesets -- score normalized to 8
Inputs used
merged_prs142
open_issues0
closed_issues2
prs_merged_7d4
prs_decided_7d4
prs_merged_30d12
prs_decided_30d12
issue_closed_ratio1
closed_unmerged_prs7
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
0/20Verified domain
18.8/25Owner reach — 415 followers of hyperbrowserai
13.9/25Track record — 22 public repos, account ~1 yr old
Inputs used
followers415
owner_typeOrganization
is_verifiedno
owner_loginhyperbrowserai
public_repos22
account_age_days724

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 1 days ago
20/20Version history — 165 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageshyperbrowser
ecosystemspypi
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

67Good · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 28 out of 28 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionno

Security

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

55Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 28 out of 28 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
6/7.5Code-Review — Found 25/30 approved changesets -- score normalized to 8
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
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
6.8/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 13 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.4
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.
How it's scored
12/35Direct dependencies free of known advisories — 1 affected: cryptography 43.0.3 (high 8.2)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
33.2/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 647 days ago
Inputs used
sourceosv
advisories22
affected_packages6
assessed_packages24
unassessed_packages0
affected_by_severitycritical 2, high 2, moderate 2
direct_affected_packages1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 24 resolved dependencies against OSV. 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.

75Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://hyperbrowser.ai/llms.txt)
40/40Legible commit history — 85 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://hyperbrowser.ai/llms.txt
legible_history_share0.85
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes4,107
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
11/11Static type checking — hyperbrowser/py.typed, pyrightconfig.json
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 18 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespoetry.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configshyperbrowser/py.typed, pyrightconfig.json
agent_commit_share0.18
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Python with type-check config (hyperbrowser/py.typed, pyrightconfig.json)
54.7/55Manageable file sizes — 1/203 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes70,541
source_files_sampled203
oversized_source_files1

Key facts

23GitHub stars
6contributors
137commits, last 12 months
1days since last push
62releases
1bus factor
0open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • deps.dev does not index pypi:hyperbrowser@1.15.6; advisories assessed against the repository dependency graph instead

More detail

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

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.

12345512025-092026-042026-10
Major 1Minor 17Patch 35
OpenSSF Scorecard 5.4 / 10
5.4aggregate

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-11-21 13:17 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests28 out of 28 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 25/30 approved changesets -- score normalized to 8
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow 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
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities13 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
PyPIpydantic>=2.0,<3pyproject.toml
PyPIhttpx>=0.23.0,<1pyproject.toml
PyPIjsonref>=1.1.0pyproject.toml
PyPIwebsockets>=13,<18pyproject.toml
PyPItyping-extensions>=4.0,<5pyproject.toml
PyPIcryptography>=41.0.0pyproject.toml
All dependencies 24

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

RegistryPackageVersionRelation
PyPIcryptography43.0.3direct
PyPIhttpx0.28.1direct
PyPIjsonref1.1.0direct
PyPIpydantic2.10.6direct
PyPItyping-extensions4.12.2direct
PyPIwebsockets13.1direct
PyPIannotated-types0.7.0indirect
PyPIanyio4.5.2indirect
PyPIcertifi2024.8.30indirect
PyPIcffi1.17.1indirect
PyPIcolorama0.4.6indirect
PyPIexceptiongroup1.2.2indirect
PyPIh110.14.0indirect
PyPIhttpcore1.0.7indirect
PyPIidna3.10indirect
PyPIiniconfig2.1.0indirect
PyPIpackaging26.0indirect
PyPIpluggy1.5.0indirect
PyPIpycparser2.23indirect
PyPIpydantic-core2.27.2indirect
PyPIpytest8.3.5indirect
PyPIruff0.3.7indirect
PyPIsniffio1.3.1indirect
PyPItomli2.4.0indirect
Dependency advisories 6

This repository publishes no package the index resolves, so its own dependency graph was assessed — 24 packages, which also include development and test pins that never ship: 6 carry known advisories, of which 1 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
anyio4.5.2indirectcritical44.14.2
h110.14.0indirectcritical20.16.0
cryptography43.0.3directhigh1049.0.0
certifi2024.8.30indirecthigh22026.10.18
idna3.10indirectmoderate23.15
pytest8.3.5indirectmoderate29.0.3

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 — PyPI.