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

spryker / product-management

[READ ONLY] Subtree split of the ProductManagement module.

PHP · TwigCustom license★ 1 star⑂ 3 forkssince Nov 2016View on GitHub ↗

spryker/product-management holds a health index of 69 out of 100, placing it in the Good band. It scores highest on Vitality (83/100) and lowest on Community & Adoption (43/100). It was last updated 1 day ago. 3 contributors account for most of its recent work.

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

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

Ownership

SprykerOrganization
114 followers1,334 public repossince Dec 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Packagistspryker/product-management0.20.1924,8991611 day ago

Metrics by category

Vitality

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

83Excellent · 21% of overall
How it's scored
36/36Push recencylast push 1 days ago
13.8/36Commit cadence20/52 weeks with commits
13.1/18Commit volume28 commits in the last year
9/10OpenSSF Scorecard: Maintained11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
Inputs used
commits_last_year28
human_commit_share1
days_since_last_push1
active_weeks_last_year20

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 1 days ago
27/27Release cadencea release every ~14.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tag0.20.19
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases14.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?

43Weak · 17% of overall
How it's scored
0/60Stars1 stars
2.5/25Forks3 forks
3.9/15Watchers6 watchers
Inputs used
forks3
stars1
watchers6
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesposer.pugx.org, shields.io
has_pull_request_templateyes
How it's scored
58.6/80Monthly downloads24,899 downloads/month across packagist
5.2/20Registry dependents5 packages depend on it
Inputs used
packagesspryker/product-management
dependents5
ecosystemspackagist
total_downloads2,761,080
monthly_downloads24,899
unverified_packages_excluded

Sustainability & Governance

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

60Moderate · 23% of overall
How it's scored
36/54Bus factor3 contributor(s) cover half of all commits
15.4/22.5Commit distributiontop contributor authored 31% of commits
13.5/13.5Contributor breadth69 contributors
10/10OpenSSF Scorecard: Contributorsproject has 12 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled69
top_contributor_share0.314
How it's scored
0/42Issue resolutionno issues or no data
0/30PR acceptance0/2 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio
closed_unmerged_prs2
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
14.8/25Owner reach114 followers of spryker
25/25Track record1,334 public repos, account ~11 yr old
Inputs used
followers114
owner_typeOrganization
is_verifiedno
owner_loginspryker
public_repos1,334
account_age_days4,297

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on packagist
35/35Publish recencylatest publish 1 days ago
20/20Version history161 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesspryker/product-management
ecosystemspackagist
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

75Good · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter configphpstan.neon
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://spryker.com
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepagehttps://spryker.com
docs_sitehttps://spryker.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

45Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
3.8/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
0/2.5CI-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 12 contributing companies or organizations
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
6.8/7.5Maintained11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTno SAST tool detected
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.5
Excluded from scoring (no data or not applicable): CI-Tests, 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.

45Weak · 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.spryker.com/llms.txt)
37.3/40Legible commit history70 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.spryker.com/llms.txt
legible_history_share0.7
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configphpstan.neon
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
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 codePHP without a type-check config
55/55Manageable file sizes0/170 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes37,927
source_files_sampled170
oversized_source_files0

Key facts

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

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 3 ⇿
0Stars
3Forks
38Releases

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.

12233312020-022022-062024-10
Major 0Minor 0Patch 38

Each point covers 5 days.

OpenSSF Scorecard 4.5 / 10
4.5aggregate

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-17 04:37 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 12 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
9Maintained11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 30
RegistryPackageVersion constraintManifest
Packagisteveron/collection^1.0.0composer.json
Packagistspryker/availability^9.0.0composer.json
Packagistspryker/category^3.0.0 || ^4.0.0 || ^5.0.0composer.json
Packagistspryker/currency^3.2.0 || ^4.0.0composer.json
Packagistspryker/decimal-object^1.0.0composer.json
Packagistspryker/gui^4.1.0 || ^5.6.0composer.json
Packagistspryker/kernel^3.30.0composer.json
Packagistspryker/locale^3.0.0 || ^4.0.0composer.json
Packagistspryker/money^2.4.0composer.json
Packagistspryker/price^5.0.0composer.json
Packagistspryker/price-product^2.1.0 || ^4.0.0composer.json
Packagistspryker/product^6.26.0composer.json
Packagistspryker/product-attribute^1.9.0composer.json
Packagistspryker/product-bundle^2.0.0 || ^3.0.0 || ^4.0.0 || ^6.0.0 || ^7.0.0composer.json
Packagistspryker/product-category^4.12.1composer.json
Packagistspryker/product-group^1.0.0composer.json
Packagistspryker/product-image^3.0.0composer.json
Packagistspryker/product-management-extension^1.11.0composer.json
Packagistspryker/product-validity^1.0.0composer.json
Packagistspryker/propel-orm^1.0.0composer.json
Packagistspryker/stock^8.0.0composer.json
Packagistspryker/store^1.28.0composer.json
Packagistspryker/symfony^3.21.0composer.json
Packagistspryker/tax^4.0.0 || ^5.0.0composer.json
Packagistspryker/touch^3.0.0 || ^4.0.0composer.json
Packagistspryker/transfer^3.27.0composer.json
Packagistspryker/translator^1.1.0composer.json
Packagistspryker/twig^3.16.0composer.json
Packagistspryker/util-encoding^2.0.0composer.json
Packagistspryker/util-text^1.1.0composer.json
All dependencies 42

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

RegistryPackageVersionRelation
Packagisteveron/collectiondirect
Packagistspryker/availabilitydirect
Packagistspryker/categorydirect
Packagistspryker/currencydirect
Packagistspryker/decimal-objectdirect
Packagistspryker/guidirect
Packagistspryker/kerneldirect
Packagistspryker/localedirect
Packagistspryker/moneydirect
Packagistspryker/pricedirect
Packagistspryker/price-productdirect
Packagistspryker/productdirect
Packagistspryker/product-attributedirect
Packagistspryker/product-bundledirect
Packagistspryker/product-categorydirect
Packagistspryker/product-groupdirect
Packagistspryker/product-imagedirect
Packagistspryker/product-management-extensiondirect
Packagistspryker/product-validitydirect
Packagistspryker/propel-ormdirect
Packagistspryker/stockdirect
Packagistspryker/storedirect
Packagistspryker/symfonydirect
Packagistspryker/taxdirect
Packagistspryker/touchdirect
Packagistspryker/transferdirect
Packagistspryker/translatordirect
Packagistspryker/twigdirect
Packagistspryker/util-encodingdirect
Packagistspryker/util-textdirect
Packagistphpindirect
Packagistspryker/applicationindirect
Packagistspryker/code-snifferindirect
Packagistspryker/containerindirect
Packagistspryker/event-dispatcherindirect
Packagistspryker/formindirect
Packagistspryker/propelindirect
Packagistspryker/routerindirect
Packagistspryker/testifyindirect
Packagistspryker/util-numberindirect
Packagistspryker/validatorindirect
Packagistspryker/zed-navigationindirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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.