Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-15 13:09 UTC

in2code-de / femanager

Modern TYPO3 Frontend User RegistrationTYPO3 Frontend User Registration and Management based on Extbase and Fluid and on TYPO3 (version 8 or newer) and the possibility to extend it to your needs.

PHP · HTMLNo license detected★ 50 stars⑂ 119 forkssince May 2017View on GitHub ↗

in2code-de/femanager holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (92/100) and lowest on Community & Adoption (45/100). It was last updated today. 2 contributors account for most of its recent work.

84
overall / 100
Excellent

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.

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

Ownership

In2code GmbHOrganization
28 followers98 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
Packagistin2code/femanager13.3.314,3739453 days agoformregistrationprofilefrontendtypo3fe-userssr-feuser-register

Metrics by category

Vitality

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

90Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
20.1/36Commit cadence29/52 weeks with commits
18/18Commit volume180 commits in the last year
10/10OpenSSF Scorecard: Maintained18 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year180
human_commit_share
days_since_last_push0
active_weeks_last_year29

Release discipline

100Exceptional
How it's scored
27/27Ships releases64 releases published
36/36Release recencylatest release 53 days ago
27/27Release cadencea release every ~26.6 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count64
latest_release_tag13.3.3
releases_from_tagsno
days_since_latest_release53
mean_days_between_releases26.6
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
27.4/60Stars50 stars
17.3/25Forks119 forks
7.1/15Watchers20 watchers
Inputs used
forks119
stars50
watchers20
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5Licenseno 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_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
55.4/80Monthly downloads14,373 downloads/month across packagist
5.6/20Registry dependents6 packages depend on it
Inputs used
packagesin2code/femanager
dependents6
ecosystemspackagist
total_downloads796,723
monthly_downloads14,373
unverified_packages_excluded

Sustainability & Governance

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

77Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
14.6/22.5Commit distributiontop contributor authored 35% of commits
13.5/13.5Contributor breadth84 contributors
10/10OpenSSF Scorecard: Contributorsproject has 22 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled84
top_contributor_share0.353
How it's scored
34.7/42Issue resolution83% of issues closed
23.8/30PR acceptance195/246 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 5/25 approved changesets -- score normalized to 2
Inputs used
merged_prs195
open_issues78
closed_issues370
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.826
closed_unmerged_prs51
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
10.5/25Owner reach28 followers of in2code-de
25/25Track record98 public repos, account ~11 yr old
Inputs used
followers28
owner_typeOrganization
is_verified
owner_loginin2code-de
public_repos98
account_age_days4,162
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on packagist
35/35Publish recencylatest publish 53 days ago
20/20Version history94 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesin2code/femanager
ecosystemspackagist
any_deprecatedno
min_days_since_publish53

Engineering Quality

Are baseline engineering and documentation practices in place?

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

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://www.in2code.de/agentur/typo3-extensions/femanager/
10/10Repository description
10/10Topics4 topics
10/10Wiki
Inputs used
topicstypo3, typo3-cms-extension, frontend-users, registration
has_wikiyes
homepagehttps://www.in2code.de/agentur/typo3-extensions/femanager/
docs_sitehttps://www.in2code.de/agentur/typo3-extensions/femanager/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

46Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2/2.5CI-Tests4 out of 5 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-ReviewFound 5/25 approved changesets -- score normalized to 2
2.5/2.5Contributorsproject has 22 contributing companies or organizations
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
0/2.5Licenselicense file not detected
7.5/7.5Maintained18 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesno data
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_aggregate4.6
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.

50Moderate · 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.php, phpstan.neon
0/11Static type checking
10/10Reproducible environmentDockerfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/165 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes37,045
source_files_sampled165
oversized_source_files0

Key facts

50GitHub stars
84contributors
180commits, last 12 months
0days since last push
64releases
2bus factor
78open issues
Packagistpackage ecosystems

More detail

OpenSSF Scorecard 4.6 / 10
4.6aggregate

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-07-15 13:08 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during GetBranch(main): error during branchesHandler.query: 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-Tests4 out of 5 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/25 approved changesets -- score normalized to 2
10Contributorsproject has 22 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
10Maintained18 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
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 7
RegistryPackageVersion constraintManifest
Packagistsymfony/config^6.4 || ^7.0composer.json
Packagisttypo3/cms-backend^13.4.0composer.json
Packagisttypo3/cms-core^13.4.0composer.json
Packagisttypo3/cms-extbase^13.4.0composer.json
Packagisttypo3/cms-fluid^13.4.0composer.json
Packagisttypo3/cms-frontend^13.4.0composer.json
Packagisttypo3/cms-seo^13.4composer.json
All dependencies 54

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

RegistryPackageVersionRelation
Packagistsymfony/configdirect
Packagisttypo3/cms-backenddirect
Packagisttypo3/cms-coredirect
Packagisttypo3/cms-extbasedirect
Packagisttypo3/cms-fluiddirect
Packagisttypo3/cms-frontenddirect
Packagisttypo3/cms-seodirect
npmgulp^4.0.0indirect
npmgulp-plumber^1.0.1indirect
npmgulp-rename^1.2.2indirect
npmgulp-sass^5.1.0indirect
npmgulp-terser^2.1.0indirect
npmgulp-uglify^1.5.1indirect
npmnpm-run-all^4.1.5indirect
npmsass^1.62.0indirect
Packagistbehat/behatindirect
Packagistbehat/mink-selenium2-driverindirect
Packagistdrevops/behat-screenshotindirect
Packagistext-intlindirect
Packagistext-jsonindirect
Packagistext-pdoindirect
Packagistfriends-of-behat/mink-browserkit-driverindirect
Packagistfriends-of-behat/mink-extensionindirect
Packagistfriendsofphp/php-cs-fixerindirect
Packagistgenesis/behat-fail-aidindirect
Packagisthelhum/typo3-consoleindirect
Packagisthelmich/typo3-typoscript-lintindirect
Packagistmikey179/vfsstreamindirect
Packagistphpindirect
Packagistphpmd/phpmdindirect
Packagistphpstan/extension-installerindirect
Packagistphpstan/phpstanindirect
Packagistphpunit/phpunitindirect
Packagistsaschaegerer/phpstan-typo3indirect
Packagistse/selenium-server-standaloneindirect
Packagistsjbr/sr-freecapindirect
Packagisttypo3/cms-adminpanelindirect
Packagisttypo3/cms-belogindirect
Packagisttypo3/cms-beuserindirect
Packagisttypo3/cms-dashboardindirect
Packagisttypo3/cms-extensionmanagerindirect
Packagisttypo3/cms-feloginindirect
Packagisttypo3/cms-filelistindirect
Packagisttypo3/cms-fluid-styled-contentindirect
Packagisttypo3/cms-impexpindirect
Packagisttypo3/cms-infoindirect
Packagisttypo3/cms-lowlevelindirect
Packagisttypo3/cms-recyclerindirect
Packagisttypo3/cms-rte-ckeditorindirect
Packagisttypo3/cms-schedulerindirect
Packagisttypo3/cms-setupindirect
Packagisttypo3/cms-styleguideindirect
Packagisttypo3/cms-tstemplateindirect
Packagisttypo3/testing-frameworkindirect
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.11.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsPackagist.