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

Aerendir / component-array-writer

A class to write arrays

PHP · DockerfileMIT★ 1 star⑂ 0 forkssince May 2016View on GitHub ↗

Aerendir/component-array-writer holds a health index of 57 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (78/100) and lowest on Community & Adoption (29/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Adamo CrespiPersonal account
37 followers49 public repossince Jul 2012@SerendipityHQ

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
Packagistserendipity_hq/component-array-writer6.0.21,52327553 days agoarray

Metrics by category

Vitality

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

44Weak · 21% of overall
How it's scored
36/36Push recencylast push 1 days ago
0/36Commit cadence35/52 weeks with commits, discounted for automation: 0 of the last 100 commits human-authored, spanning 107 days
0/18Commit volume238 commits in the last year, discounted for automation: 0 of the last 100 commits human-authored, spanning 107 days
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year238
human_commit_share0
days_since_last_push1
active_weeks_last_year35
How it's scored
16.2/27Ships releases27 version tags (no GitHub releases)
7.2/36Release recencylatest release 553 days ago
12.6/27Release cadencea release every ~181.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count27
latest_release_tag6.0.2
releases_from_tagsyes
days_since_latest_release553
mean_days_between_releases181.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?

29At Risk · 17% of overall
How it's scored
0/60Stars1 stars
0/25Forks0 forks
0/15Watchers1 watchers
Inputs used
forks0
stars1
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges22
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, github.com, shields.io, sonarcloud.io
has_pull_request_templateno
How it's scored
42.4/80Monthly downloads1,523 downloads/month across packagist
3.2/20Registry dependents2 packages depend on it
Inputs used
packagesserendipity_hq/component-array-writer
dependents2
ecosystemspackagist
total_downloads391,511
monthly_downloads1,523
unverified_packages_excluded

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

57Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.1/22.5Commit distributiontop contributor authored 100% of commits
2.7/13.5Contributor breadth2 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.997
How it's scored
38.2/42Issue resolution91% of issues closed
25.5/30PR acceptance802/945 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Reviewno data
Inputs used
merged_prs802
open_issues1
closed_issues10
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.909
closed_unmerged_prs143
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, OpenSSF Scorecard: Code-Review. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
11.4/25Owner reach37 followers of Aerendir
24.4/25Track record49 public repos, account ~14 yr old
Inputs used
followers37
owner_typeUser
is_verified
owner_loginAerendir
public_repos49
account_age_days5,167
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on packagist
14/35Publish recencylatest publish 553 days ago
20/20Version history27 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesserendipity_hq/component-array-writer
ecosystemspackagist
any_deprecatedno
min_days_since_publish553

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall
How it's scored
24/24CI workflows6 workflow(s)
24/24Tests present
16/16Linter config.php-cs-fixer.dist.php, phpstan.neon
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests16 out of 16 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

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics1 topics
10/10Wiki
Inputs used
topicsarray
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?

68Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests16 out of 16 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-Reviewno data
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
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
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate6
Excluded from scoring (no data or not applicable): Branch-Protection, Code-Review, Dangerous-Workflow, Packaging, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages8
unassessed_packages11
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 8 resolved dependencies against OSV. 11 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

43Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
11/11Lint / format config.php-cs-fixer.dist.php, phpstan.neon
0/11Static type checking
10/10Reproducible environmentDockerfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance50 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.5
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/7 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes15,401
source_files_sampled7
oversized_source_files0

Key facts

1GitHub stars
2contributors
238commits, last 12 months
1days since last push
27releases
1bus factor
1open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

OpenSSF Scorecard 6.0 / 10
6.0aggregate

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 16:16 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-Tests16 out of 16 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
n/aCode-ReviewFound no human activity in the last 16 changesets
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
n/aDangerous-Workflowno workflows found
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
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
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
Packagistsymfony/property-access^6.4 || ^7.4 || ^8.0composer.json
Packagistthecodingmachine/safe^2.0 || ^3.0composer.json
All dependencies 19

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

RegistryPackageVersionRelation
Packagistsymfony/property-accessdirect
Packagistthecodingmachine/safedirect
Packagistaerendir/bin-github-actions-matrixindirect
Packagistbamarni/composer-bin-pluginindirect
Packagistergebnis/composer-normalizeindirect
Packagistfriendsofphp/php-cs-fixer3.95.24indirect
Packagistinfection/infectionindirect
Packagistphpindirect
Packagistphpstan/phpstan2.2.8indirect
Packagistphpstan/phpstan-phpunit2.0.18indirect
Packagistphpunit/phpunitindirect
Packagistpsalm/plugin-phpunit0.19.5indirect
Packagistrector/rector2.6.1indirect
Packagistroave/security-advisoriesindirect
Packagistserendipity_hq/phpcs-config1.2.5indirect
Packagistserendipity_hq/rector-config1.1.20indirect
Packagistsymfony/phpunit-bridgeindirect
Packagistthecodingmachine/phpstan-safe-rule1.4.7indirect
Packagistvimeo/psalmindirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 8 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 11 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

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