Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-22 15:19 UTC

tomasnorre / crawler

Libraries and scripts for crawling the TYPO3 page tree. Used for re-caching, re-indexing, publishing applications etc.

PHPGPL-3.0★ 57 stars⑂ 90 forkssince Jan 2015View on GitHub ↗
KindPluginCommand-line toolhow this is determined

tomasnorre/crawler holds a health index of 89 out of 100, placing it in the Excellent band. It scores highest on Vitality (84/100) and lowest on Sustainability & Governance (67/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Tomas Norre MikkelsenPersonal account
52 followers203 public repossince Nov 20117th Green

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 publish
Packagisttomasnorre/crawler12.0.118,25488102 days ago

Metrics by category

Vitality

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

84Excellent · 21% of overall
How it's scored
36/36Push recencylast push 4 days ago
20.8/36Commit cadence30/52 weeks with commits
18/18Commit volume122 commits in the last year
10/10OpenSSF Scorecard: Maintained13 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year122
human_commit_share0.89
days_since_last_push4
active_weeks_last_year30
How it's scored
27/27Ships releases36 releases published
27/36Release recencylatest release 102 days ago
19.8/27Release cadencea release every ~79.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count36
latest_release_tag12.0.11
releases_from_tagsno
days_since_latest_release102
mean_days_between_releases79.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?

67Good · 17% of overall
How it's scored
28.4/60Stars57 stars
16.2/25Forks90 forks
8/15Watchers28 watchers
Inputs used
forks90
stars57
watchers28
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (GPL-3.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicescoveralls.io, github.com, poser.pugx.org, shields.io
has_pull_request_templateyes
How it's scored
52.2/80Monthly downloads8,254 downloads/month across packagist
3.2/20Registry dependents2 packages depend on it
Inputs used
packagestomasnorre/crawler
dependents2
ecosystemspackagist
total_downloads444,162
monthly_downloads8,254
unverified_packages_excluded

Sustainability & Governance

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

67Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
5.6/22.5Commit distributiontop contributor authored 75% of commits
13.5/13.5Contributor breadth60 contributors
10/10OpenSSF Scorecard: Contributorsproject has 22 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled60
top_contributor_share0.75
How it's scored
40.6/42Issue resolution97% of issues closed
26.9/30PR acceptance752/839 decided PRs merged
13/13Newcomer PR acceptance2/2 first-time contributors' PRs merged in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 5/25 approved changesets -- score normalized to 2
Inputs used
merged_prs752
open_issues16
closed_issues453
prs_merged_7d1
prs_decided_7d1
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio0.966
closed_unmerged_prs87
first_time_authors_30d1
first_time_prs_merged_30d2
first_time_prs_decided_30d2
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
12.4/25Owner reach52 followers of tomasnorre
25/25Track record203 public repos, account ~14 yr old
Inputs used
followers52
owner_typeUser
is_verified
owner_logintomasnorre
public_repos203
account_age_days5,387
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 102 days ago
20/20Version history88 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagestomasnorre/crawler
ecosystemspackagist
any_deprecatedno
min_days_since_publish102

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows12 workflow(s)
24/24Tests present
16/16Linter configphpstan.neon
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests24 out of 24 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
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics7 topics
0/10Wiki
Inputs used
topicstypo3, extension, crawler, cache-warmup, php, indexer, hacktoberfest
has_wikino
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

76Good · 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-Tests24 out of 24 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
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
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained13 commit(s) and 6 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
5/5Security-Policysecurity policy file 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_aggregate7
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 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_packages6
unassessed_packages49
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 6 resolved dependencies against OSV. 49 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.

69Good · 4% of overall
How it's scored
0/45Agent instructionsno 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.4/40Legible commit history59 of 89 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.663
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
11/11Lint / format configphpstan.neon
0/11Static type checking
10/10Reproducible environmentDockerfile, lockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance11 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileyes
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.11
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/184 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes32,172
source_files_sampled184
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
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

57GitHub stars
60contributors
122commits, last 12 months
4days since last push
36releases
1bus factor
16open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch packagist package 'tomasnorre/crawler-devbox' from its registry

More detail

Star and fork history 0 ★ / 90 ⇿
0Stars
90Forks
36Releases

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.

0204060801008932015-062021-012026-07
Major 3Minor 3Patch 30

Each point covers 11 days.

OpenSSF Scorecard 7.0 / 10
7.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-08-22 15:18 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-Tests24 out of 24 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 5/25 approved changesets -- score normalized to 2
10Contributorsproject has 22 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained13 commit(s) and 6 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
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 26
RegistryPackageVersion constraintManifest
Packagistgeorgringer/news^14.devbox/composer.json
Packagisttnm/crawler-devbox-sitepackage^0.0.5.devbox/composer.json
Packagisttomasnorre/crawler*@dev.devbox/composer.json
Packagisttypo3/cms-belog^13.4 || ^14.3.devbox/composer.json
Packagisttypo3/cms-beuser^13.4 || ^14.3.devbox/composer.json
Packagisttypo3/cms-felogin^13.4 || ^14.3.devbox/composer.json
Packagisttypo3/cms-indexed-search^13.4 || ^14.3.devbox/composer.json
Packagisttypo3/cms-info^13.4 || ^14.3.devbox/composer.json
Packagisttypo3/cms-install^13.4 || ^14.3.devbox/composer.json
Packagisttypo3/cms-scheduler^13.4 || ^14.3.devbox/composer.json
Packagisttypo3/cms-tstemplate^13.4 || ^14.3.devbox/composer.json
Packagisttypo3/minimal^13.4 || ^14.3.devbox/composer.json
Packagistbeberlei/assert^3.3composer.json
Packagistdoctrine/dbal^3.10 || ^4.3composer.json
Packagistguzzlehttp/guzzle^6.4.1 || ^7.2composer.json
Packagistpsr/http-message^2.0composer.json
Packagistpsr/http-server-handler^1.0composer.json
Packagistpsr/http-server-middleware^1.0composer.json
Packagistpsr/log^1.0 || ^2.0 || ^3.0composer.json
Packagistsymfony/console^7.2composer.json
Packagistsymfony/service-contracts^3.6composer.json
Packagisttypo3/cms-backend^13.4 || ^14.3composer.json
Packagisttypo3/cms-core^13.4 || ^14.3composer.json
Packagisttypo3/cms-extbase^13.4 || ^14.3composer.json
Packagisttypo3/cms-frontend^13.4 || ^14.3composer.json
Packagisttypo3/cms-info^13.4 || ^14.3composer.json
All dependencies 55

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

RegistryPackageVersionRelation
Packagistbeberlei/assertdirect
Packagistdoctrine/dbaldirect
Packagistgeorgringer/newsdirect
Packagistguzzlehttp/guzzledirect
Packagistpsr/http-messagedirect
Packagistpsr/http-server-handlerdirect
Packagistpsr/http-server-middlewaredirect
Packagistpsr/logdirect
Packagistsymfony/consoledirect
Packagistsymfony/service-contractsdirect
Packagisttnm/crawler-devbox-sitepackagedirect
Packagisttomasnorre/crawlerdirect
Packagisttypo3/cms-backenddirect
Packagisttypo3/cms-belogdirect
Packagisttypo3/cms-beuserdirect
Packagisttypo3/cms-coredirect
Packagisttypo3/cms-extbasedirect
Packagisttypo3/cms-felogindirect
Packagisttypo3/cms-frontenddirect
Packagisttypo3/cms-indexed-searchdirect
Packagisttypo3/cms-infodirect
Packagisttypo3/cms-installdirect
Packagisttypo3/cms-schedulerdirect
Packagisttypo3/cms-tstemplatedirect
Packagisttypo3/minimaldirect
npm@playwright/test1.56.1indirect
npm@types/node22.18.12indirect
npmfsevents2.3.2indirect
npmplaywright1.56.1indirect
npmplaywright-core1.56.1indirect
npmundici-types6.21.0indirect
Packagistext-jsonindirect
Packagistext-pdoindirect
Packagistext-posixindirect
Packagisthelhum/typo3-consoleindirect
Packagistinfection/infectionindirect
Packagistnikic/php-parserindirect
Packagistphpindirect
Packagistphpspec/prophecy-phpunitindirect
Packagistphpstan/extension-installerindirect
Packagistphpstan/phpstanindirect
Packagistphpstan/phpstan-deprecation-rulesindirect
Packagistphpunit/phpunitindirect
Packagistroave/security-advisoriesindirect
Packagistsbuerk/typo3-cmscomposerinstallers-testingframework-bridgeindirect
Packagistshipmonk/composer-dependency-analyserindirect
Packagistssch/typo3-rectorindirect
Packagistsymfony/yamlindirect
Packagistsymplify/easy-coding-standardindirect
Packagistsymplify/phpstan-rulesindirect
Packagisttomasvotruba/cognitive-complexityindirect
Packagisttomasvotruba/type-coverageindirect
Packagisttypo3/cms-seoindirect
Packagisttypo3/testing-frameworkindirect
Packagistvimeo/psalmindirect
Dependency advisories 0

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