Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 14:41 UTC

pagemachine / typo3-formlog

Form log for TYPO3

PHP · HTMLGPL-3.0★ 23 stars⑂ 20 forkssince Feb 2018View on GitHub ↗
KindPluginLibraryhow this is determined

pagemachine/typo3-formlog holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Engineering Quality (78/100) and lowest on Security (42/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

67
overall / 100
Good

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.

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

Ownership

Pagemachine AGOrganization
6 followers23 public repossince Feb 2015

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistpagemachine/typo3-formlog2.6.04,7334499 days agologformtypo3

Metrics by category

Vitality

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

74Good · 21% of overall
How it's scored
36/36Push recency — last push 4 days ago
7.6/36Commit cadence — 11/52 weeks with commits
14.8/18Commit volume — 44 commits in the last year
5/10OpenSSF Scorecard: Maintained — 6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year44
human_commit_share0.93
days_since_last_push4
active_weeks_last_year11
How it's scored
27/27Ships releases — 26 releases published
27/36Release recency — latest release 99 days ago
27/27Release cadence — a release every ~21.4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count26
latest_release_tag2.6.0
releases_from_tagsno
days_since_latest_release99
mean_days_between_releases21.4
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?

45Weak · 17% of overall
How it's scored
21.8/60Stars — 23 stars
10.7/25Forks — 20 forks
3.9/15Watchers — 6 watchers
Inputs used
forks20
stars23
watchers6
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonbelow_threshold
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (GPL-3.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com
has_pull_request_templateno
How it's scored
49/80Monthly downloads — 4,733 downloads/month across packagist
5.2/20Registry dependents — 5 packages depend on it
Inputs used
packagespagemachine/typo3-formlog
dependents5
ecosystemspackagist
total_downloads249,458
monthly_downloads4,733
unverified_packages_excluded—

Sustainability & Governance

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

61Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.2/22.5Commit distribution — top contributor authored 95% of commits
9.5/13.5Contributor breadth — 7 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled7
top_contributor_share0.946
How it's scored
32.9/42Issue resolution — 78% of issues closed
28/30PR acceptance — 233/250 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/11 approved changesets -- score normalized to 0
Inputs used
merged_prs233
open_issues11
closed_issues40
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.784
closed_unmerged_prs17
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. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
6.1/25Owner reach — 6 followers of pagemachine
22.1/25Track record — 23 public repos, account ~11 yr old
Inputs used
followers6
owner_typeOrganization
is_verifiedno
owner_loginpagemachine
public_repos23
account_age_days4,239

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 99 days ago
20/20Version history — 44 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagespagemachine/typo3-formlog
ecosystemspackagist
any_deprecatedno
min_days_since_publish99

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall
How it's scored
24/24CI workflows — 1 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-Tests — 12 out of 12 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/10Topics — 4 topics
10/10Wiki
Inputs used
topicstypo3, typo3-cms-extension, form, logging
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?

42Weak · 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 — 12 out of 12 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/11 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 4 contributing companies or organizations
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
3.8/7.5Maintained — 6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate4.2
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

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.

52Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://docs.typo3.org/llms.txt)
29.8/40Legible commit history — 52 of 93 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.typo3.org/llms.txt
legible_history_share0.559
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .php-cs-fixer.dist.php, phpstan.neon
0/11Static type checking
10/10Reproducible environment — Dockerfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 7 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.07
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — PHP without a type-check config
55/55Manageable file sizes — 0/46 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes9,061
source_files_sampled46
oversized_source_files0

Key facts

23GitHub stars
7contributors
44commits, last 12 months
4days since last push
26releases
1bus factor
11open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2025-10-29: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 23 stars today.
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 23 ★ / 20 ⇿
23Stars
20Forks
22Releases

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.

Star history is shown as collected on 2025-10-29. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

04812162024232022018-022022-032026-03
Major 1Minor 4Patch 17

Each point covers 8 days.

OpenSSF Scorecard 4.2 / 10
4.2aggregate

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-12 14:40 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-Tests12 out of 12 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/11 approved changesets -- score normalized to 0
10Contributorsproject has 4 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
5Maintained6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
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 13
RegistryPackageVersion constraintManifest
Packagistleague/csv^9.1composer.json
Packagistnimmneun/onesheet^1.0composer.json
Packagistpsr/http-factory^1.0composer.json
Packagistpsr/http-message^1.0 || ^2.0composer.json
Packagistpsr/log^1.0 || ^2.0 || ^3.0composer.json
Packagisttypo3/cms-backend^13.4 || ^14.2composer.json
Packagisttypo3/cms-core^13.4 || ^14.2composer.json
Packagisttypo3/cms-extbase^13.4 || ^14.2composer.json
Packagisttypo3/cms-fluid^13.4 || ^14.2composer.json
Packagisttypo3/cms-form^13.4 || ^14.2composer.json
Packagisttypo3/cms-frontend^13.4 || ^14.2composer.json
Packagisttypo3/cms-install^13.4 || ^14.2composer.json
Packagisttypo3fluid/fluid^2.3 || ^4.0 || ^5.0composer.json
All dependencies 32

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

RegistryPackageVersionRelation
Packagistleague/csv—direct
Packagistnimmneun/onesheet—direct
Packagistpsr/http-factory—direct
Packagistpsr/http-message—direct
Packagistpsr/log—direct
Packagisttypo3/cms-backend—direct
Packagisttypo3/cms-core—direct
Packagisttypo3/cms-extbase—direct
Packagisttypo3/cms-fluid—direct
Packagisttypo3/cms-form—direct
Packagisttypo3/cms-frontend—direct
Packagisttypo3/cms-install—direct
Packagisttypo3fluid/fluid—direct
Packagistergebnis/composer-normalize—indirect
Packagistfriendsofphp/php-cs-fixer—indirect
Packagisthelmich/typo3-typoscript-lint—indirect
Packagistjangregor/phpstan-prophecy—indirect
Packagistmichielroos/typo3scan—indirect
Packagistphp—indirect
Packagistphp-parallel-lint/php-console-highlighter—indirect
Packagistphp-parallel-lint/php-parallel-lint—indirect
Packagistphpspec/prophecy-phpunit—indirect
Packagistphpstan/phpstan—indirect
Packagistphpunit/phpunit—indirect
Packagistrector/rector—indirect
Packagistsaschaegerer/phpstan-typo3—indirect
Packagistsclable/xml-lint—indirect
Packagistssch/typo3-rector—indirect
Packagisttypo3/cms-fluid-styled-content—indirect
Packagisttypo3/cms-scheduler—indirect
Packagisttypo3/coding-standards—indirect
Packagisttypo3/testing-framework—indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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 — Packagist.