Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-21 17:32 UTC

extcode / cart

Cart is a small but powerful extension which "solely" adds a shopping cart to your TYPO3 installation. The extension allows you to create coupons, products with or without variants, special prices.

PHP · HTMLGPL-2.0★ 59 stars⑂ 57 forkssince Mar 2016View on GitHub ↗
KindPluginLibraryhow this is determined

extcode/cart holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Engineering Quality (84/100) and lowest on Security (60/100). It was last updated 10 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Daniel GohlkePersonal account
33 followers45 public repossince Oct 2011

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
Packagistextcode/cartv12.0.03,25319577 days agocartshopping-carttypo3-cms

Metrics by category

Vitality

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

69Good · 21% of overall
How it's scored
28.8/36Push recency — last push 10 days ago
9/36Commit cadence — 13/52 weeks with commits
14.9/18Commit volume — 45 commits in the last year
4/10OpenSSF Scorecard: Maintained — 5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
Inputs used
commits_last_year45
human_commit_share1
days_since_last_push10
active_weeks_last_year13
How it's scored
16.2/27Ships releases — 100 version tags (no GitHub releases)
36/36Release recency — latest release 77 days ago
27/27Release cadence — a release every ~39.4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv12.0.0
releases_from_tagsyes
days_since_latest_release77
mean_days_between_releases39.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?

61Moderate · 17% of overall
How it's scored
28.6/60Stars — 59 stars
14.6/25Forks — 57 forks
5.6/15Watchers — 11 watchers
Inputs used
forks57
stars59
watchers11
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (GPL-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
7.2/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingyes
has_issue_templateyes
has_code_of_conductno
readme_badge_servicesgithub.com
has_pull_request_templateno
How it's scored
46.8/80Monthly downloads — 3,253 downloads/month across packagist
8/20Registry dependents — 15 packages depend on it
Inputs used
packagesextcode/cart
dependents15
ecosystemspackagist
total_downloads137,597
monthly_downloads3,253
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
7.3/22.5Commit distribution — top contributor authored 68% of commits
13.5/13.5Contributor breadth — 25 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled25
top_contributor_share0.677
How it's scored
38.4/42Issue resolution — 92% of issues closed
24.1/30PR acceptance — 197/245 decided PRs merged
6.5/13Newcomer PR acceptance — 1/2 first-time contributors' PRs merged in 30d
3/15OpenSSF Scorecard: Code-Review — Found 5/18 approved changesets -- score normalized to 2
Inputs used
merged_prs197
open_issues44
closed_issues471
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d3
issue_closed_ratio0.915
closed_unmerged_prs48
first_time_authors_30d2
first_time_prs_merged_30d1
first_time_prs_decided_30d2
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
11/25Owner reach — 33 followers of extcode
24.1/25Track record — 45 public repos, account ~15 yr old
Inputs used
followers33
owner_typeUser
is_verified—
owner_loginextcode
public_repos45
account_age_days5,482
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 packagist
35/35Publish recency — latest publish 77 days ago
20/20Version history — 195 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesextcode/cart
ecosystemspackagist
any_deprecatedno
min_days_since_publish77

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — .php-cs-fixer.dist.php, eslint.config.mjs, phpstan.neon
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests — 14 out of 17 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

80Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://cart.extco.de
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
docs_sitehttps://cart.extco.de
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

60Moderate · 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/2.5CI-Tests — 14 out of 17 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-Review — Found 5/18 approved changesets -- score normalized to 2
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflow — no data
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
3/7.5Maintained — 5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
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_aggregate5
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages1
unassessed_packages36
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 1 resolved dependencies against OSV. 36 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.

64Moderate · 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.9/40Legible commit history — 56 of 100 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.56
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
11/11Lint / format config — .php-cs-fixer.dist.php, eslint.config.mjs, phpstan.neon
0/11Static type checking
10/10Reproducible environment — Nix
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixyes
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
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/298 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes39,304
source_files_sampled298
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

59GitHub stars
25contributors
45commits, last 12 months
10days since last push
100releases
1bus factor
44open issues
Packagistpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 57 ⇿
0Stars
57Forks
100Releases

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.

01020304050605722016-102021-092026-08
Major 5Minor 27Patch 68

Each point covers 10 days.

OpenSSF Scorecard 5.0 / 10
5.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-10-21 17:31 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
8CI-Tests14 out of 17 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 5/18 approved changesets -- score normalized to 2
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
4Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
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 4
RegistryPackageVersion constraintManifest
Packagisttypo3/cms-core^14.3composer.json
Packagisttypo3/cms-extbase^14.3composer.json
Packagisttypo3/cms-fluid^14.3composer.json
Packagisttypo3/cms-frontend^14.3composer.json
All dependencies 37

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

RegistryPackageVersionRelation
Packagisttypo3/cms-core—direct
Packagisttypo3/cms-extbase—direct
Packagisttypo3/cms-fluid—direct
Packagisttypo3/cms-frontend—direct
npm@eslint/eslintrc^3.0.2indirect
npm@eslint/js^9.0.0indirect
npm@stylistic/eslint-plugin^1.7.0indirect
npmesbuild0.25.0indirect
npmeslint^8.57.0indirect
npmeslint-config-airbnb^19.0.4indirect
npmeslint-config-standard^17.1.0indirect
npmeslint-plugin-import^2.29.1indirect
npmeslint-plugin-jsx-a11y^6.8.0indirect
npmeslint-plugin-n^16.6.2indirect
npmeslint-plugin-promise^6.1.1indirect
npmeslint-plugin-react^7.34.1indirect
npmeslint-plugin-react-hooks^4.6.0indirect
npmglobals^15.0.0indirect
Packagistcodappix/typo3-php-datasets—indirect
Packagisterickskrauch/php-cs-fixer-custom-fixers—indirect
Packagistext-json—indirect
Packagistext-openssl—indirect
Packagistextcode/cart—indirect
Packagistfriendsofphp/php-cs-fixer—indirect
Packagistkubawerlos/php-cs-fixer-custom-fixers—indirect
Packagistphp—indirect
Packagistphpstan/extension-installer—indirect
Packagistphpstan/phpstan—indirect
Packagistphpstan/phpstan-deprecation-rules—indirect
Packagistphpstan/phpstan-phpunit—indirect
Packagistspaze/phpstan-disallowed-calls—indirect
Packagistssch/typo3-rector—indirect
Packagiststaabm/phpstan-todo-by—indirect
Packagisttypo3/cms-beuser—indirect
Packagisttypo3/cms-dashboard—indirect
Packagisttypo3/cms-form—indirect
Packagisttypo3/testing-framework—indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 1 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 36 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 statistics — Packagist.