Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-04 15:37 UTC

patchlevel / event-sourcing-dashboard-bundle

This bundle provides web ui interfaces for the patchlevel/event-sourcing.

Twig · PHPMIT★ 3 stars⑂ 0 forkssince Jun 2026View on GitHub ↗
KindPluginLibraryWeb interfacehow this is determined

patchlevel/event-sourcing-dashboard-bundle holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Vitality (84/100) and lowest on Community & Adoption (32/100). It was last updated today. A single contributor accounts for most of its recent work.

63
overall / 100
Moderate

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.

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

Ownership

patchlevelOrganization
16 followers23 public repossince Aug 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistpatchlevel/event-sourcing-dashboard-bundle1.0.0-alpha96,511176 days agosymfonybundledashboardevent-sourcingpatchlevel

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 0 days ago
29.8/36Commit cadence43/52 weeks with commits
18/18Commit volume221 commits in the last year
0/10OpenSSF Scorecard: Maintainedproject was created within the last 90 days. Please review its contents carefully
Inputs used
commits_last_year221
human_commit_share0.13
days_since_last_push0
active_weeks_last_year43
How it's scored
27/27Ships releases1 releases published
36/36Release recencylatest release 76 days ago
12.6/27Release cadencecadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count1
latest_release_tag1.0.0-alpha9
releases_from_tagsno
days_since_latest_release76
mean_days_between_releases
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?

32At Risk · 17% of overall
How it's scored
4.9/60Stars3 stars
0/25Forks0 forks
0/15Watchers1 watchers
Inputs used
forks0
stars3
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesposer.pugx.org
has_pull_request_templateno
How it's scored
50.8/80Monthly downloads6,511 downloads/month across packagist
0/20Registry dependents0 packages depend on it
Inputs used
packagespatchlevel/event-sourcing-dashboard-bundle
dependents0
ecosystemspackagist
total_downloads6,560
monthly_downloads6,511
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 factor1 contributor(s) cover half of all commits
8.6/22.5Commit distributiontop contributor authored 62% of commits
4.1/13.5Contributor breadth3 contributors
10/10OpenSSF Scorecard: Contributorsproject has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.619
How it's scored
0/42Issue resolutionno issues or no data
30/30PR acceptance3/3 decided PRs merged
13/13Newcomer PR acceptance3/3 first-time contributors' PRs merged in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 3/27 approved changesets -- score normalized to 1
Inputs used
merged_prs3
open_issues0
closed_issues0
prs_merged_7d3
prs_decided_7d3
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio
closed_unmerged_prs0
first_time_authors_30d1
first_time_prs_merged_30d3
first_time_prs_decided_30d3
Excluded from scoring (no data or not applicable): Issue resolution. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
8.8/25Owner reach16 followers of patchlevel
22.1/25Track record23 public repos, account ~6 yr old
Inputs used
followers16
owner_typeOrganization
is_verifiedno
owner_loginpatchlevel
public_repos23
account_age_days2,220
How it's scored
25/25Published & resolvable1 package(s) on packagist
35/35Publish recencylatest publish 76 days ago
4/20Version history1 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagespatchlevel/event-sourcing-dashboard-bundle
ecosystemspackagist
any_deprecatedno
min_days_since_publish76

Engineering Quality

Are baseline engineering and documentation practices in place?

73Good · 19% of overall
How it's scored
24/24CI workflows10 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests3 out of 3 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

80Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://patchlevel.dev/docs/event-sourcing-dashboard-bundle/latest
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepage
docs_sitehttps://patchlevel.dev/docs/event-sourcing-dashboard-bundle/latest
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

36Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests3 out of 3 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
0.8/7.5Code-ReviewFound 3/27 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 4 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintainedproject was created within the last 90 days. Please review its contents carefully
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
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-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities43 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.6
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. 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.

46Weak · 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://patchlevel.dev/llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtyes
llms_txt_urlhttps://patchlevel.dev/llms.txt
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
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance87 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilescomposer.lock, package-lock.json
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.87
How it's scored
0/45Type-checkable codeTwig without a type-check config
55/55Manageable file sizes0/34 source files over 60KB
Inputs used
primary_languageTwig
largest_source_bytes8,934
source_files_sampled34
oversized_source_files0

Key facts

3GitHub stars
3contributors
221commits, last 12 months
0days since last push
1releases
1bus factor
0open issues
npm, Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

OpenSSF Scorecard 3.6 / 10
3.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-09-04 15:37 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests3 out of 3 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 3/27 approved changesets -- score normalized to 1
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintainedproject was created within the last 90 days. Please review its contents carefully
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
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities43 existing vulnerabilities detected
Direct dependencies 11
RegistryPackageVersion constraintManifest
Packagistpatchlevel/event-sourcing^3.8.0composer.json
Packagistpatchlevel/event-sourcing-bundle^3.7.0composer.json
Packagistsymfony/asset^5.4.33 || ^6.4.1 || ^7.0.1 || ^8.0.0composer.json
Packagistsymfony/asset-mapper^6.4.1 || ^7.0.1 || ^8.0.0composer.json
Packagistsymfony/config^5.4.31 || ^6.4.0 || ^7.0.0 || ^8.0.0composer.json
Packagistsymfony/dependency-injection^5.4.33 || ^6.4.1 || ^7.0.1 || ^8.0.0composer.json
Packagistsymfony/expression-language^5.4.33 || ^6.4.1 || ^7.0.1 || ^8.0.0composer.json
Packagistsymfony/http-kernel^5.4.33 || ^6.4.1 || ^7.0.1 || ^8.0.0composer.json
Packagistsymfony/routing^5.4.33 || ^6.4.1 || ^7.0.1 || ^8.0.0composer.json
Packagistsymfony/var-dumper^5.4.29 || ^6.4.0 || ^7.0.0 || ^8.0.0composer.json
Packagisttwig/twig^3.20.0composer.json
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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.