Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-11 10:33 UTC

teamneusta / pw_comments

Powerful TYPO3 CMS extension for providing comments, including replies on comments and votings, as well as mail notifications.

PHPNo license detected★ 1 star⑂ 10 forkssince Sep 2023View on GitHub ↗

teamneusta/pw_comments holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Engineering Quality (86/100) and lowest on Community & Adoption (24/100). It was last updated 31 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

team neusta SEOrganization · verified domain
23 followers37 public repossince Jun 2015

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistteamneusta/pw_comments8.0.13,8131854 days agocommentextensiontypo3voting

Metrics by category

Vitality

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

67Good · 21% of overall
How it's scored
18/36Push recency — last push 31 days ago
4.8/36Commit cadence — 7/52 weeks with commits
18/18Commit volume — 275 commits in the last year
9/10OpenSSF Scorecard: Maintained — 9 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 9
Inputs used
commits_last_year275
human_commit_share1
days_since_last_push31
active_weeks_last_year7
How it's scored
27/27Ships releases — 11 releases published
36/36Release recency — latest release 54 days ago
19.8/27Release cadence — a release every ~86.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count11
latest_release_tag7.1.2
releases_from_tagsno
days_since_latest_release54
mean_days_between_releases86.9
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?

24At Risk · 17% of overall
How it's scored
0/60Stars — 1 stars
8/25Forks — 10 forks
0/15Watchers — 0 watchers
Inputs used
forks10
stars1
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5License — no license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
47.8/80Monthly downloads — 3,813 downloads/month across packagist
2/20Registry dependents — 1 packages depend on it
Inputs used
packagesteamneusta/pw_comments
dependents1
ecosystemspackagist
total_downloads71,912
monthly_downloads3,813
unverified_packages_excluded—

Sustainability & Governance

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

71Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
9/22.5Commit distribution — top contributor authored 60% of commits
13.5/13.5Contributor breadth — 14 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled14
top_contributor_share0.601
How it's scored
42/42Issue resolution — 100% of issues closed
25.7/30PR acceptance — 36/42 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-Review — Found 1/5 approved changesets -- score normalized to 2
Inputs used
merged_prs36
open_issues0
closed_issues29
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs6
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
20/20Verified domain
9.9/25Owner reach — 23 followers of teamneusta
23.5/25Track record — 37 public repos, account ~11 yr old
Inputs used
followers23
owner_typeOrganization
is_verifiedyes
owner_loginteamneusta
public_repos37
account_age_days4,104

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 54 days ago
20/20Version history — 18 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesteamneusta/pw_comments
ecosystemspackagist
any_deprecatedno
min_days_since_publish54

Engineering Quality

Are baseline engineering and documentation practices in place?

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

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://extensions.typo3.org/extension/pw_comments
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepagehttps://extensions.typo3.org/extension/pw_comments
docs_sitehttps://extensions.typo3.org/extension/pw_comments
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

50Moderate · 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 — 4 out of 4 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
1.5/7.5Code-Review — Found 1/5 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
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
0/2.5License — license file not detected
6.8/7.5Maintained — 9 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 9
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
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_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate3.8
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, 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
advisories25
affected_packages10
assessed_packages143
unassessed_packages10
affected_by_severitycritical 3, high 6, moderate 1
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 143 resolved dependencies against OSV. 10 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.

58Moderate · 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)
35.7/40Legible commit history — 67 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.67
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
11/11Static type checking — Build/tsconfig.json
10/10Reproducible environment — Dockerfile, lockfile
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 — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configsBuild/tsconfig.json
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — PHP with type-check config (Build/tsconfig.json)
54.3/55Manageable file sizes — 1/76 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes82,378
source_files_sampled76
oversized_source_files1

Key facts

1GitHub stars
14contributors
275commits, last 12 months
31days since last push
11releases
1bus factor
0open issues
npm, 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 ★ / 10 ⇿
0Stars
10Forks
9Releases

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.

02468101012023-122025-032026-07
Major 3Minor 1Patch 5

Each point covers 3 days.

OpenSSF Scorecard 3.8 / 10
3.8aggregate

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-11 10:32 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-Tests4 out of 4 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 1/5 approved changesets -- score normalized to 2
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
9Maintained9 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 9
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 5
RegistryPackageVersion constraintManifest
Packagisttypo3/cms-core^14.3composer.json
Packagisttypo3/cms-backend^14.3composer.json
Packagisttypo3/cms-extbase^14.3composer.json
Packagisttypo3/cms-frontend^14.3composer.json
Packagisttypo3/cms-install^14.3composer.json
All dependencies 153

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

RegistryPackageVersionRelation
Packagisttypo3/cms-backend—direct
Packagisttypo3/cms-core—direct
Packagisttypo3/cms-extbase—direct
Packagisttypo3/cms-frontend—direct
Packagisttypo3/cms-install—direct
npm@asamuzakjp/css-color3.2.0indirect
npm@csstools/color-helpers5.0.2indirect
npm@csstools/css-calc2.1.4indirect
npm@csstools/css-color-parser3.0.10indirect
npm@csstools/css-parser-algorithms3.0.5indirect
npm@csstools/css-tokenizer3.0.4indirect
npm@esbuild/aix-ppc640.25.5indirect
npm@esbuild/android-arm0.25.5indirect
npm@esbuild/android-arm640.25.5indirect
npm@esbuild/android-x640.25.5indirect
npm@esbuild/darwin-arm640.25.5indirect
npm@esbuild/darwin-x640.25.5indirect
npm@esbuild/freebsd-arm640.25.5indirect
npm@esbuild/freebsd-x640.25.5indirect
npm@esbuild/linux-arm0.25.5indirect
npm@esbuild/linux-arm640.25.5indirect
npm@esbuild/linux-ia320.25.5indirect
npm@esbuild/linux-loong640.25.5indirect
npm@esbuild/linux-mips64el0.25.5indirect
npm@esbuild/linux-ppc640.25.5indirect
npm@esbuild/linux-riscv640.25.5indirect
npm@esbuild/linux-s390x0.25.5indirect
npm@esbuild/linux-x640.25.5indirect
npm@esbuild/netbsd-arm640.25.5indirect
npm@esbuild/netbsd-x640.25.5indirect
npm@esbuild/openbsd-arm640.25.5indirect
npm@esbuild/openbsd-x640.25.5indirect
npm@esbuild/sunos-x640.25.5indirect
npm@esbuild/win32-arm640.25.5indirect
npm@esbuild/win32-ia320.25.5indirect
npm@esbuild/win32-x640.25.5indirect
npm@jridgewell/sourcemap-codec1.5.0indirect
npm@polka/url1.0.0-next.29indirect
npm@rollup/rollup-android-arm-eabi4.44.1indirect
npm@rollup/rollup-android-arm644.44.1indirect
npm@rollup/rollup-darwin-arm644.44.1indirect
npm@rollup/rollup-darwin-x644.44.1indirect
npm@rollup/rollup-freebsd-arm644.44.1indirect
npm@rollup/rollup-freebsd-x644.44.1indirect
npm@rollup/rollup-linux-arm-gnueabihf4.44.1indirect
npm@rollup/rollup-linux-arm-musleabihf4.44.1indirect
npm@rollup/rollup-linux-arm64-gnu4.44.1indirect
npm@rollup/rollup-linux-arm64-musl4.44.1indirect
npm@rollup/rollup-linux-loongarch64-gnu4.44.1indirect
npm@rollup/rollup-linux-powerpc64le-gnu4.44.1indirect
npm@rollup/rollup-linux-riscv64-gnu4.44.1indirect
npm@rollup/rollup-linux-riscv64-musl4.44.1indirect
npm@rollup/rollup-linux-s390x-gnu4.44.1indirect
npm@rollup/rollup-linux-x64-gnu4.44.1indirect
npm@rollup/rollup-linux-x64-musl4.44.1indirect
npm@rollup/rollup-win32-arm64-msvc4.44.1indirect
npm@rollup/rollup-win32-ia32-msvc4.44.1indirect
npm@rollup/rollup-win32-x64-msvc4.44.1indirect
npm@types/chai5.2.2indirect
npm@types/deep-eql4.0.2indirect
npm@types/estree1.0.8indirect
npm@types/jsdom21.1.7indirect
npm@types/node24.0.4indirect
npm@types/tough-cookie4.0.5indirect
npm@vitest/expect3.2.4indirect
npm@vitest/mocker3.2.4indirect
npm@vitest/pretty-format3.2.4indirect
npm@vitest/runner3.2.4indirect
npm@vitest/snapshot3.2.4indirect
npm@vitest/spy3.2.4indirect
npm@vitest/ui3.2.4indirect
npm@vitest/utils3.2.4indirect
npmagent-base7.1.3indirect
npmassertion-error2.0.1indirect
npmcac6.7.14indirect
npmchai5.2.0indirect
npmcheck-error2.1.1indirect
npmcssstyle4.6.0indirect
npmdata-urls5.0.0indirect
npmdebug4.4.1indirect
npmdecimal.js10.5.0indirect
npmdeep-eql5.0.2indirect
npmentities6.0.1indirect
npmes-module-lexer1.7.0indirect
npmesbuild0.25.5indirect
npmestree-walker3.0.3indirect
npmexpect-type1.2.1indirect
npmfdir6.4.6indirect
npmfflate0.8.2indirect
npmflatted3.3.3indirect
npmfsevents2.3.3indirect
npmhtml-encoding-sniffer4.0.0indirect
npmhttp-proxy-agent7.0.2indirect
npmhttps-proxy-agent7.0.6indirect
npmiconv-lite0.6.3indirect
npmis-potential-custom-element-name1.0.1indirect
npmjs-tokens9.0.1indirect
npmjsdom26.1.0indirect
npmloupe3.1.4indirect
npmlru-cache10.4.3indirect
npmmagic-string0.30.17indirect
npmmrmime2.0.1indirect
npmms2.1.3indirect
npmnanoid3.3.11indirect
npmnwsapi2.2.20indirect
npmparse57.3.0indirect
npmpathe2.0.3indirect
npmpathval2.0.1indirect
npmpicocolors1.1.1indirect
npmpicomatch4.0.2indirect
npmpostcss8.5.6indirect
npmpunycode2.3.1indirect
npmrollup4.44.1indirect
npmrrweb-cssom0.8.0indirect
npmsafer-buffer2.1.2indirect
npmsaxes6.0.0indirect
npmsiginfo2.0.0indirect
npmsirv3.0.1indirect
npmsource-map-js1.2.1indirect
npmstackback0.0.2indirect
npmstd-env3.9.0indirect
npmstrip-literal3.0.0indirect
npmsymbol-tree3.2.4indirect
npmtinybench2.9.0indirect
npmtinyexec0.3.2indirect
npmtinyglobby0.2.14indirect
npmtinypool1.1.1indirect
npmtinyrainbow2.0.0indirect
npmtinyspy4.0.3indirect
npmtldts6.1.86indirect
npmtldts-core6.1.86indirect
npmtotalist3.0.1indirect
npmtough-cookie5.1.2indirect
npmtr465.1.1indirect
npmtypescript5.8.3indirect
npmundici-types7.8.0indirect
npmvite7.0.0indirect
npmvite-node3.2.4indirect
npmvitest3.2.4indirect
npmw3c-xmlserializer5.0.0indirect
npmwebidl-conversions7.0.0indirect
npmwhatwg-encoding3.1.1indirect
npmwhatwg-mimetype4.0.0indirect
npmwhatwg-url14.2.0indirect
npmwhy-is-node-running2.3.0indirect
npmws8.18.2indirect
npmxml-name-validator5.0.0indirect
npmxmlchars2.2.0indirect
Packagistphp—indirect
Packagistphpunit/phpcov—indirect
Packagistphpunit/phpunit—indirect
Packagistroave/security-advisories—indirect
Packagisttypo3/testing-framework—indirect
Dependency advisories 10

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

PackageVersionRelationSeverityAdvisoriesFixed in
flatted3.3.3indirectcritical23.4.2
rollup4.44.1indirectcritical14.59.0
vitest3.2.4indirectcritical25.0.0-rc.2
fflate0.8.2indirecthigh10.8.3
nanoid3.3.11indirecthigh35.1.16
picomatch4.0.2indirecthigh24.0.4
postcss8.5.6indirecthigh48.5.23
vite7.0.0indirecthigh78.0.16
ws8.18.2indirecthigh28.21.0
@vitest/mocker3.2.4indirectmoderate15.0.0-rc.2

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.