Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-21 05:38 UTC

ryanrosello-og / playwright-slack-report

Publish your Playwright test results to your favourite Slack channel(s).

TypeScript · JavaScriptMIT★ 149 stars⑂ 47 forkssince Jul 2022View on GitHub ↗
KindCommand-line toolLibraryWeb interfacehow this is determined

ryanrosello-og/playwright-slack-report holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on AI Readiness (89/100) and lowest on Sustainability & Governance (59/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

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

Ownership

ryanrosello-ogPersonal account
15 followers24 public repossince May 2019

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmplaywright-slack-report1.1.117830,5056010 days agoslackreportplaywrighttypescript

Metrics by category

Vitality

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

84Excellent · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
9.7/36Commit cadence — 14/52 weeks with commits
18/18Commit volume — 105 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year105
human_commit_share0.32
days_since_last_push1
active_weeks_last_year14

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 60 releases published
36/36Release recency — latest release 10 days ago
27/27Release cadence — a release every ~25.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count60
latest_release_tagv1.1.117
releases_from_tagsno
days_since_latest_release10
mean_days_between_releases25.8
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?

71Good · 17% of overall
How it's scored
35.2/60Stars — 149 stars
13.9/25Forks — 47 forks
0/15Watchers — 2 watchers
Inputs used
forks47
stars149
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicescoveralls.io, github.com, shields.io
has_pull_request_templateyes
How it's scored
78.9/80Monthly downloads — 830,505 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesplaywright-slack-report
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads830,505
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?

59Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
4.6/22.5Commit distribution — top contributor authored 79% of commits
13.5/13.5Contributor breadth — 18 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled18
top_contributor_share0.794
How it's scored
40.6/42Issue resolution — 97% of issues closed
20.7/30PR acceptance — 269/389 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/14 approved changesets -- score normalized to 0
Inputs used
merged_prs269
open_issues3
closed_issues89
prs_merged_7d5
prs_decided_7d5
prs_merged_30d18
prs_decided_30d18
issue_closed_ratio0.967
closed_unmerged_prs120
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
8.7/25Owner reach — 15 followers of ryanrosello-og
22.2/25Track record — 24 public repos, account ~7 yr old
Inputs used
followers15
owner_typeUser
is_verified—
owner_loginryanrosello-og
public_repos24
account_age_days2,717
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 10 days ago
20/20Version history — 60 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesplaywright-slack-report
ecosystemsnpm
any_deprecatedno
min_days_since_publish10

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.js
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 29 out of 29 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

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 4 topics
10/10Wiki
Inputs used
topicsplaywright, slack, test-automation, typescript
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

67Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 29 out of 29 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
0/7.5Code-Review — Found 0/14 approved changesets -- score normalized to 0
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 3 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
5/5SAST — SAST tool is run on all commits
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
0/7.5Vulnerabilities — 24 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.9
Excluded from scoring (no data or not applicable): Branch-Protection, 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_packages22
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:playwright-slack-report@1.1.117 runtime dependency closure — what installing the published package pulls in — 22 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.

89Excellent · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md
15/15Machine-readable docs (llms.txt) — llms.txt present
40/40Legible commit history — 30 of 32 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_url—
legible_history_share0.938
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes5,366
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.js
11/11Static type checking — tsconfig.json
10/10Reproducible environment — devcontainer
10/10Demonstrated agent practice — 5 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 68 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontaineryes
has_linter_configyes
typecheck_configstsconfig.json
agent_commit_share0.05
toolchain_manifests—
dependency_bot_commit_share0.68
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
55/55Manageable file sizes — 0/70 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes58,487
source_files_sampled70
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
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

149GitHub stars
18contributors
105commits, last 12 months
1days since last push
60releases
1bus factor
3open 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 ★ / 47 ⇿
0Stars
47Forks
54Releases

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.

010203040504752022-092024-102026-10
Major 0Minor 1Patch 52

Each point covers 4 days.

OpenSSF Scorecard 5.9 / 10
5.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-10-21 05:37 UTC

10Binary-Artifactsno binaries found in the repo
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
10CI-Tests29 out of 29 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/14 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 3 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
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
0Vulnerabilities24 existing vulnerabilities detected
Direct dependencies 14
RegistryPackageVersion constraintManifest
npm@slack/web-api^8.2.0package.json
npm@slack/webhook^8.0.2package.json
npmcommander^15.0.0package.json
npmhttps-proxy-agent^7.0.6package.json
npmundici^8.11.1package.json
npmzod^4.6.5package.json
npm@docusaurus/core3.10.2website/package.json
npm@docusaurus/preset-classic3.10.2website/package.json
npm@easyops-cn/docusaurus-search-local0.55.3website/package.json
npm@mdx-js/react^3.0.1website/package.json
npmclsx^2.1.1website/package.json
npmprism-react-renderer^2.4.1website/package.json
npmreact^19.0.0website/package.json
npmreact-dom^19.0.0website/package.json
All dependencies 39

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

RegistryPackageVersionRelation
npm@docusaurus/core3.10.2direct
npm@docusaurus/preset-classic3.10.2direct
npm@easyops-cn/docusaurus-search-local0.55.3direct
npm@mdx-js/react^3.0.1direct
npm@slack/web-api^8.2.0direct
npm@slack/webhook^8.0.2direct
npmclsx^2.1.1direct
npmcommander^15.0.0direct
npmhttps-proxy-agent^7.0.6direct
npmprism-react-renderer^2.4.1direct
npmreact^19.0.0direct
npmreact-dom^19.0.0direct
npmundici^8.11.1direct
npmzod^4.6.5direct
npm@eslint/js^10.0.1indirect
npm@playwright/test1.64.0indirect
npm@playwright/test^1.64.0indirect
npm@slack/types^3.0.0indirect
npm@types/bun1.4.2indirect
npm@types/node>=26.6.4indirect
npm@typescript-eslint/eslint-plugin^8.71.2indirect
npm@typescript-eslint/parser^8.71.1indirect
npmdotenv^18.0.6indirect
npmeslint^10.12.0indirect
npmeslint-config-airbnb-base^15.0.0indirect
npmeslint-config-prettier^10.1.8indirect
npmeslint-import-resolver-typescript^4.4.5indirect
npmeslint-plugin-import^2.32.0indirect
npmeslint-plugin-node^11.1.0indirect
npmeslint-plugin-prettier^5.5.6indirect
npmglobals^17.13.0indirect
npmistanbul-lib-coverage3.2.2indirect
npmistanbul-lib-instrument6.0.3indirect
npmistanbul-lib-report3.0.1indirect
npmistanbul-reports3.2.0indirect
npmprettier^3.9.9indirect
npmts-sinon^2.0.2indirect
npmtypescript^5.9.3indirect
npmtypescript-eslint^8.71.1indirect
Dependency advisories 0

Installing npm:playwright-slack-report@1.1.117 pulls in 22 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.

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.