Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-05 23:08 UTC

xynogen / pix-mono

Monorepo of Pix, Distro of PI Coding Agent

TypeScriptMIT★ 64 stars⑂ 12 forkssince Jun 2026View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

xynogen/pix-mono holds a health index of 56 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (70/100) and lowest on Vitality (38/100). It was last updated today. A single contributor accounts for most of its recent work.

56
overall / 100
Moderate

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.

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

Ownership

Muhammad FikriPersonal account
10 followers37 public repossince Jun 2018PT. Pupuk Sriwijaya

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

Package ecosystems

Metrics by category

Vitality

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

38Weak · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
9/36Commit cadence13/52 weeks with commits
18/18Commit volume621 commits in the last year
0/10OpenSSF Scorecard: Maintainedproject was created within the last 90 days. Please review its contents carefully
Inputs used
commits_last_year621
human_commit_share1
days_since_last_push0
active_weeks_last_year13
How it's scored
0/27Ships releasesno releases published
0/36Release recencyno releases
0/27Release cadenceno releases
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count0
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?

58Moderate · 17% of overall
How it's scored
29.2/60Stars64 stars
8.7/25Forks12 forks
0/15Watchers2 watchers
Inputs used
forks12
stars64
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
58.3/80Monthly downloads23,635 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@xynogen/pix-ls, @xynogen/pix-ask, @xynogen/pix-env, @xynogen/pix-mcp, @xynogen/pix-bash, @xynogen/pix-core, @xynogen/pix-data, @xynogen/pix-edit
dependents
ecosystemsnpm
total_downloads
monthly_downloads23,635
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?

54Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.5/22.5Commit distributiontop contributor authored 98% of commits
9.5/13.5Contributor breadth7 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled7
top_contributor_share0.978
How it's scored
21/42Issue resolution50% of issues closed
27/30PR acceptance9/10 decided PRs merged
10.4/13Newcomer PR acceptance4/5 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 1/30 approved changesets -- score normalized to 0
Inputs used
merged_prs9
open_issues3
closed_issues3
prs_merged_7d2
prs_decided_7d2
prs_merged_30d4
prs_decided_30d5
issue_closed_ratio0.5
closed_unmerged_prs1
first_time_authors_30d3
first_time_prs_merged_30d4
first_time_prs_decided_30d5
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
7.5/25Owner reach10 followers of xynogen
23.5/25Track record37 public repos, account ~8 yr old
Inputs used
followers10
owner_typeUser
is_verified
owner_loginxynogen
public_repos37
account_age_days3,008
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable8 package(s) on npm
35/35Publish recencylatest publish 0 days ago
20/20Version history94 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@xynogen/pix-ls, @xynogen/pix-ask, @xynogen/pix-env, @xynogen/pix-mcp, @xynogen/pix-bash, @xynogen/pix-core, @xynogen/pix-data, @xynogen/pix-edit
ecosystemsnpm
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter configbiome.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests1 out of 1 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

50Moderate
How it's scored
30/30README
0/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_dirno
has_descriptionyes

Security

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

51Moderate · 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
2.5/2.5CI-Tests1 out of 1 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 1/30 approved changesets -- score normalized to 0
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintainedproject was created within the last 90 days. Please review its contents carefully
0/5Packagingno data
3/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 6
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
6.8/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
3/7.5Vulnerabilities6 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.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages53
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:@xynogen/pix-ls@0.2.4 runtime dependency closure — what installing the published package pulls in — 53 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
How it's scored
45/45Agent instructionsAGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history98 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.98
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes17,888
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configbiome.json
11/11Static type checkingpackages/pix-mcp/tsconfig.json, packages/pix-pretty/src/tsconfig.json, packages/pix-search/tsconfig.json
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
6/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 6
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configspackages/pix-mcp/tsconfig.json, packages/pix-pretty/src/tsconfig.json, packages/pix-search/tsconfig.json
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeTypeScript (statically typed)
54.9/55Manageable file sizes1/405 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes295,508
source_files_sampled405
oversized_source_files1
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
20/20MCP server
0/40Runnable examples
Inputs used
example_dirs
has_mcp_signalyes
api_schema_files
interfaces_expected_of
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto). Remaining weights renormalized.

Key facts

64GitHub stars
7contributors
621commits, last 12 months
0days since last push
0releases
1bus factor
3open 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 ★ / 12 ⇿
0Stars
12Forks

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.

0246810121212026-062026-072026-08
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-09-05 23:08 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests1 out of 1 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 1/30 approved changesets -- score normalized to 0
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
0Maintainedproject was created within the last 90 days. Please review its contents carefully
n/aPackagingpackaging workflow not detected
6Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 6
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
4Vulnerabilities6 existing vulnerabilities detected
Direct dependencies 73
RegistryPackageVersion constraintManifest
npm@xynogen/pix-pretty^1.19.0packages/pix-9router/package.json
npmtypebox^1.1.38packages/pix-9router/package.json
npm@xynogen/pix-runtime^0.8.0packages/pix-9router/package.json
npm@xynogen/pix-pretty^1.21.0packages/pix-ask/package.json
npm@xynogen/pix-runtime^0.8.0packages/pix-ask/package.json
npmtypebox^1.1.38packages/pix-ask/package.json
npm@xynogen/pix-pretty^1.19.0packages/pix-bash/package.json
npm@xynogen/pix-runtime^0.8.0packages/pix-bash/package.json
npm@xynogen/pix-data^0.4.0packages/pix-commands/package.json
npm@xynogen/pix-pretty^1.13.0packages/pix-commands/package.json
npm@xynogen/pix-runtime^0.8.0packages/pix-commands/package.json
npm@xynogen/pix-runtime^0.8.4packages/pix-core/package.json
npm@xynogen/pix-data^0.4.7packages/pix-core/package.json
npm@xynogen/pix-pretty^1.21.0packages/pix-core/package.json
npm@xynogen/pix-welcome^0.2.2packages/pix-core/package.json
npm@xynogen/pix-footer^0.2.3packages/pix-core/package.json
npm@xynogen/pix-diagnostics^0.2.3packages/pix-core/package.json
npm@xynogen/pix-display^0.1.17packages/pix-core/package.json
npm@xynogen/pix-prompts^0.4.5packages/pix-core/package.json
npm@xynogen/pix-skills^0.8.4packages/pix-core/package.json
npm@xynogen/pix-models^0.2.5packages/pix-core/package.json
npm@xynogen/pix-update^0.2.2packages/pix-core/package.json
npm@xynogen/pix-commands^0.6.4packages/pix-core/package.json
npm@xynogen/pix-nudge^0.2.4packages/pix-core/package.json
npm@xynogen/pix-read^0.2.4packages/pix-core/package.json
npm@xynogen/pix-write^0.2.4packages/pix-core/package.json
npm@xynogen/pix-edit^0.2.4packages/pix-core/package.json
npm@xynogen/pix-find^0.2.4packages/pix-core/package.json
npm@xynogen/pix-grep^0.2.5packages/pix-core/package.json
npm@xynogen/pix-ls^0.2.4packages/pix-core/package.json
npm@xynogen/pix-bash^0.2.4packages/pix-core/package.json
npm@xynogen/pix-todo^0.3.3packages/pix-core/package.json
npm@xynogen/pix-ask^0.2.29packages/pix-core/package.json
npm@xynogen/pix-optimizer^1.1.29packages/pix-core/package.json
npm@xynogen/pix-gate^0.2.13packages/pix-core/package.json
npm@xynogen/pix-subagent^0.8.0packages/pix-core/package.json
npm@xynogen/pix-runtime^0.8.0packages/pix-data/package.json
npm@xynogen/pix-runtime^0.8.0packages/pix-diagnostics/package.json
npm@xynogen/pix-pretty^1.11.2packages/pix-display/package.json
npm@xynogen/pix-pretty^1.19.0packages/pix-edit/package.json
npm@xynogen/pix-runtime^0.8.0packages/pix-edit/package.json
npm@xynogen/pix-pretty^1.16.0packages/pix-env/package.json
npm@xynogen/pix-runtime^0.8.0packages/pix-env/package.json
npm@xynogen/pix-pretty^1.19.0packages/pix-find/package.json
npm@xynogen/pix-runtime^0.8.0packages/pix-find/package.json
npm@xynogen/pix-data^0.4.3packages/pix-footer/package.json
npm@xynogen/pix-pretty^1.11.2packages/pix-footer/package.json
npm@xynogen/pix-runtime^0.8.0packages/pix-footer/package.json
npm@xynogen/pix-pretty^1.11.2packages/pix-gate/package.json
npm@xynogen/pix-runtime^0.8.0packages/pix-gate/package.json
npm@xynogen/pix-pretty^1.19.0packages/pix-graph/package.json
npm@xynogen/pix-runtime^0.8.0packages/pix-graph/package.json
npmtypebox^1.1.38packages/pix-graph/package.json
npmtypescript^5.7.0packages/pix-graph/package.json
npm@xynogen/pix-pretty^1.19.0packages/pix-grep/package.json
npm@xynogen/pix-runtime^0.8.0packages/pix-grep/package.json
npm@xynogen/pix-pretty^1.19.0packages/pix-hunk/package.json
npm@xynogen/pix-runtime^0.8.1packages/pix-hunk/package.json
npmtypebox^1.1.38packages/pix-hunk/package.json
npm@xynogen/pix-pretty^1.19.0packages/pix-ls/package.json
npm@xynogen/pix-runtime^0.8.0packages/pix-ls/package.json
npm@modelcontextprotocol/client^2.0.0packages/pix-mcp/package.json
npm@modelcontextprotocol/ext-apps^1.2.2packages/pix-mcp/package.json
npm@xynogen/pix-pretty^1.19.0packages/pix-mcp/package.json
npm@xynogen/pix-runtime^0.8.0packages/pix-mcp/package.json
npmopen^10.2.0packages/pix-mcp/package.json
npmrecheck^4.5.0packages/pix-mcp/package.json
npmtypebox^1.1.38packages/pix-mcp/package.json
npmzod^3.25.0 || ^4.0.0packages/pix-mcp/package.json
npm@xynogen/pix-data^0.4.3packages/pix-models/package.json
npm@xynogen/pix-pretty^1.11.2packages/pix-models/package.json
npm@xynogen/pix-runtime^0.8.0packages/pix-models/package.json
npm@xynogen/pix-runtime^0.8.0packages/pix-nudge/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:@xynogen/pix-ls@0.2.4 pulls in 53 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 statisticsnpm.