Public record
Software health reportschema 0.31.0 · metrics 2.5.0 · 2026-08-08 01:07 UTC

anchorbrowser / AnchorBrowser-SDK-Typescript

AnchorBrowser-SDK-Typescript

TypeScriptApache-2.0★ 5 stars⑂ 0 forkssince Jul 2025View on GitHub ↗
KindLibraryhow this is determined

anchorbrowser/AnchorBrowser-SDK-Typescript holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Vitality (91/100) and lowest on Community & Adoption (50/100). It was last updated 3 days ago. 2 contributors account 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

anchorbrowserOrganization
3 followers11 public repossince Jun 2025

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmanchorbrowser1.0.0108,7015912 days agoanchorbrowseranchorbrowserautomationinfrastructureagentic-browsersdktypescriptbrowser-automationagent-apiai-agentsautomation-infracloud-browserself-healingcdpplaywrightbrowser-agentsproxycaptcha-bypassweb-scrapingform-fillingsession-managemententerprise-securitybrowser-infrastructureautonomous-web

Metrics by category

Vitality

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

91Excellent · 21% of overall

Development activity

91Excellent
How it's scored
36/36Push recency — last push 3 days ago
27/36Commit cadence — 39/52 weeks with commits
18/18Commit volume — 244 commits in the last year
10/10OpenSSF Scorecard: Maintained — 20 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year244
human_commit_share0.32
days_since_last_push3
active_weeks_last_year39

Release discipline

90Excellent
How it's scored
27/27Ships releases — 62 releases published
27/36Release recency — latest release 96 days ago
27/27Release cadence — a release every ~6.5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count62
latest_release_tagv1.0.0-dev.4
releases_from_tagsno
days_since_latest_release96
mean_days_between_releases6.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?

50Moderate · 17% of overall

Popularity & adoption

10Critical
How it's scored
9.8/60Stars — 5 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars5
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

70Good
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno

Ecosystem adoption (downloads)

84Excellent
How it's scored
67.1/80Monthly downloads — 108,701 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesanchorbrowser
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads108,701
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

Maintainer resilience (bus factor)

46Weak
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
11.9/22.5Commit distribution — top contributor authored 47% of commits
5.4/13.5Contributor breadth — 4 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor2
contributors_sampled4
top_contributor_share0.469

Issue & PR responsiveness

96Exceptional
How it's scored
42/42Issue resolution — 100% of issues closed
28.7/30PR acceptance — 68/71 decided PRs merged
9.8/13Newcomer PR acceptance — 3/4 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs68
open_issues0
closed_issues4
prs_merged_7d0
prs_decided_7d1
prs_merged_30d3
prs_decided_30d4
issue_closed_ratio1
closed_unmerged_prs3
first_time_authors_30d2
first_time_prs_merged_30d3
first_time_prs_decided_30d4

Ownership & stewardship

44Weak
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
4.3/25Owner reach — 3 followers of anchorbrowser
10.1/25Track record — 11 public repos, account ~1 yr old
Inputs used
followers3
owner_typeOrganization
is_verified—
owner_loginanchorbrowser
public_repos11
account_age_days412

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 12 days ago
20/20Version history — 59 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesanchorbrowser
ecosystemsnpm
any_deprecatedno
min_days_since_publish12

Engineering Quality

Are baseline engineering and documentation practices in place?

66Good · 19% of overall

Engineering practices

84Excellent
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.mjs
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 4 out of 4 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

40Weak
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

61Moderate · 16% of overall

Security posture

51Moderate
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 4 out of 4 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
7.5/7.5Code-Review — all changesets reviewed
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
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 — 20 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
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
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 16 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.1
Excluded from scoring (no data or not applicable): packaging, signed_releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages4
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:anchorbrowser@1.0.0 runtime dependency closure — what installing the published package pulls in — 4 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.

65Good · 4% of overall

Agent context & guidance

40Weak
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 24 of 32 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
legible_history_share0.75
agent_instruction_files—
agent_instruction_max_bytes—

Verify loop (build / test / typecheck)

64Moderate
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.mjs
11/11Static type checking — tsconfig.json
10/10Reproducible environment — devcontainer, lockfile
10/10Demonstrated agent practice — 9 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
lockfilesyarn.lock
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontaineryes
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0.09
toolchain_manifests—
dependency_bot_commit_share0

Code legibility for models

100Exceptional
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/23 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes6,254
source_files_sampled23
oversized_source_files0

Machine-readable interfaces

80Excellent
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — spec/openapi.yaml
0/20MCP server
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_filesspec/openapi.yaml

Key facts

5GitHub stars
4contributors
244commits, last 12 months
3days since last push
62releases
2bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 5.1 / 10
5.1aggregate

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-08-08 01:06 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests4 out of 4 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained20 commit(s) and 0 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
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities16 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
npmplaywright^1.57.0package.json
npmws^8.18.3package.json
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

Dependency advisories 0

Installing npm:anchorbrowser@1.0.0 pulls in 4 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

Related records

Inspected repositories sharing catalogue tags or ecosystems with anchorbrowser/AnchorBrowser-SDK-Typescript. Read them side by side →

96apify/crawleeCrawlee—A web scraping and browser automation library for Node.js to build reliable crawlers. In JavaScript and TypeScript. Extract data for AI, LLMs, RAG, or GPTs. Download HTML, PDF, JPG, PNG, and other files from websites. Works with Puppeteer, Playwright, Cheerio, JSDOM, and raw HTTP. Both headful and headless mode. With proxy rotation.Exceptional96strands-agents/harness-sdkBuild an agent harness and control it end-to-end. Open-source SDK for production AI agents in Python & TypeScript - any model, any cloud.Exceptional99PrefectHQ/prefectPrefect is a workflow orchestration framework for building resilient data pipelines in Python.Exceptional98novuhq/novuThe open-source communication infrastructure for agents and productsExceptional98kestra-io/kestraEvent Driven Orchestration & Scheduling Platform for Mission Critical ApplicationsExceptional98Azure/azure-sdk-for-jsThis repository is for active development of the Azure SDK for JavaScript (NodeJS & Browser). For consumers of the SDK we recommend visiting our public developer docs at https://docs.microsoft.com/javascript/azure/ or our versioned developer docs at https://azure.github.io/azure-sdk-for-js. Exceptional

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.5.0, schema v0.31.0 — full methodology · metrics wiki.

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