Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 18:04 UTC

pixel-agents-hq / pixel-agents

Pixel office.

TypeScript · HTMLMIT★ 9,337 stars⑂ 1,524 forkssince Feb 2026View on GitHub ↗
KindNetwork serviceLibraryCommand-line toolWeb interfacehow this is determined

pixel-agents-hq/pixel-agents holds a health index of 87 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (84/100) and lowest on Sustainability & Governance (52/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Pixel Agents HQOrganization
44 followers4 public repossince Apr 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
npmpixel-agents1.4.12,302333 days ago

Metrics by category

Vitality

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

83Excellent · 21% of overall
How it's scored
36/36Push recency — last push 4 days ago
15.2/36Commit cadence — 22/52 weeks with commits
18/18Commit volume — 219 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_year219
human_commit_share0.84
days_since_last_push4
active_weeks_last_year22
How it's scored
27/27Ships releases — 7 releases published
36/36Release recency — latest release 33 days ago
27/27Release cadence — a release every ~28.2 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count7
latest_release_tagv1.4.1
releases_from_tagsno
days_since_latest_release33
mean_days_between_releases28.2

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

84Excellent · 17% of overall
How it's scored
60/60Stars — 9,337 stars
25/25Forks — 1,524 forks
9/15Watchers — 43 watchers
Inputs used
forks1,524
stars9,337
watchers43
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges8
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateyes
How it's scored
44.8/80Monthly downloads — 2,302 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagespixel-agents
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads2,302
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?

52Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
8.8/22.5Commit distribution — top contributor authored 61% of commits
13.5/13.5Contributor breadth — 17 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled17
top_contributor_share0.61
How it's scored
27.8/42Issue resolution — 66% of issues closed
11.5/30PR acceptance — 90/234 decided PRs merged
0/13Newcomer PR acceptance — 0/3 first-time contributors' PRs merged in 30d
12/15OpenSSF Scorecard: Code-Review — Found 6/7 approved changesets -- score normalized to 8
Inputs used
merged_prs90
open_issues31
closed_issues61
prs_merged_7d0
prs_decided_7d1
prs_merged_30d0
prs_decided_30d3
issue_closed_ratio0.663
closed_unmerged_prs144
first_time_authors_30d3
first_time_prs_merged_30d0
first_time_prs_decided_30d3
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
11.9/25Owner reach — 44 followers of pixel-agents-hq
6/25Track record — 4 public repos, account ~0 yr old
Inputs used
followers44
owner_typeOrganization
is_verifiedno
owner_loginpixel-agents-hq
public_repos4
account_age_days169
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 33 days ago
12/20Version history — 3 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagespixel-agents
ecosystemsnpm
any_deprecatedno
min_days_since_publish33

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
16/16Linter config — eslint.config.js, eslint.config.mjs
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 17 out of 17 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

64Moderate · 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 — 17 out of 17 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 6/7 approved changesets -- score normalized to 8
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 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
1.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
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 — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 11 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate5.5

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_packages82
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:pixel-agents@1.4.1 runtime dependency closure — what installing the published package pulls in — 82 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.

81Excellent · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://docs.anthropic.com/llms.txt)
40/40Legible commit history — 84 of 84 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.anthropic.com/llms.txt
legible_history_share1
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes69,627
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — eslint.config.js, eslint.config.mjs
11/11Static type checking — e2e/tsconfig.json, tsconfig.json, webview-ui/tsconfig.json
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 34 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 16 of the last 100 commits are automated dependency updates
3/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configse2e/tsconfig.json, tsconfig.json, webview-ui/tsconfig.json
agent_commit_share0.34
toolchain_manifests—
dependency_bot_commit_share0.16
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
54.8/55Manageable file sizes — 1/225 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes70,564
source_files_sampled225
oversized_source_files1
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — core/asyncapi.yaml
0/20MCP server
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalno
api_schema_filescore/asyncapi.yaml
interfaces_expected_ofnetwork-service

Key facts

9,337GitHub stars
17contributors
219commits, last 12 months
4days since last push
7releases
1bus factor
31open 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

Star and fork history 0 ★ / 1,524 ⇿
0Stars
1,524Forks
6Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

4006008001,0001,2001,4001,6001,524202026-032026-062026-09
Major 0Minor 4Patch 2
OpenSSF Scorecard 5.5 / 10
5.5aggregate

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-18 18:04 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests17 out of 17 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 6/7 approved changesets -- score normalized to 8
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 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities11 existing vulnerabilities detected
Direct dependencies 10
RegistryPackageVersion constraintManifest
npm@fastify/cors^11.2.0package.json
npm@fastify/static^10.1.2package.json
npm@fastify/websocket^11.2.0package.json
npmfastify^5.8.5package.json
npm@fastify/cors^11.2.0server/package.json
npm@fastify/static^10.1.2server/package.json
npm@fastify/websocket^11.2.0server/package.json
npmfastify^5.8.5server/package.json
npmreact^19.2.5webview-ui/package.json
npmreact-dom^19.2.5webview-ui/package.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:pixel-agents@1.4.1 pulls in 82 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.