Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-13 21:31 UTC

spryker / sales-order-amendment-extension

[READ ONLY] Subtree split of the SalesOrderAmendmentExtension module.

PHPCustom license★ 0 stars⑂ 0 forkssince Nov 2024View on GitHub ↗
KindLibraryhow this is determined

spryker/sales-order-amendment-extension holds a health index of 31 out of 100, placing it in the At Risk band. It scores highest on Engineering Quality (57/100) and lowest on AI Readiness (17/100). It was last updated 315 days ago. 2 contributors account for most of its recent work.

31
overall / 100
At Risk

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.

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

Ownership

SprykerOrganization
113 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/sales-order-amendment-extension1.3.019,1414399 days ago

Metrics by category

Vitality

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

26At Risk · 21% of overall

Development activity

4Critical
How it's scored
3.6/36Push recency — last push 315 days ago
0/36Commit cadence — 0/52 weeks with commits
0/18Commit volume — 0 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share—
days_since_last_push315
active_weeks_last_year0

Release discipline

60Moderate
How it's scored
27/27Ships releases — 4 releases published
7.2/36Release recency — latest release 399 days ago
19.8/27Release cadence — a release every ~78.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count4
latest_release_tag1.3.0
releases_from_tagsno
days_since_latest_release399
mean_days_between_releases78.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?

42Weak · 17% of overall

Popularity & adoption

2Critical
How it's scored
0/60Stars — 0 stars
0/25Forks — 0 forks
1.7/15Watchers — 3 watchers
Inputs used
forks0
stars0
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

71Good
How it's scored
22.5/22.5README
16.9/22.5License — license 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

Ecosystem adoption (downloads)

65Good
How it's scored
57.1/80Monthly downloads — 19,141 downloads/month across packagist
8/20Registry dependents — 15 packages depend on it
Inputs used
packagesspryker/sales-order-amendment-extension
dependents15
ecosystemspackagist
total_downloads282,495
monthly_downloads19,141
unverified_packages_excluded—

Sustainability & Governance

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

50Moderate · 23% of overall

Maintainer resilience (bus factor)

47Weak
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
15/22.5Commit distribution — top contributor authored 33% of commits
6.8/13.5Contributor breadth — 5 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor2
contributors_sampled5
top_contributor_share0.333

Issue & PR responsiveness

1Critical
How it's scored
0/42Issue resolution — no issues or no data
0/30PR acceptance — no decided pull requests or no data
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/6 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_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

87Excellent
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain — verified-domain status not read for this organization
14.8/25Owner reach — 113 followers of spryker
25/25Track record — 1,334 public repos, account ~11 yr old
Inputs used
followers113
owner_typeOrganization
is_verified—
owner_loginspryker
public_repos1,334
account_age_days4,263
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

71Good
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
14/35Publish recency — latest publish 399 days ago
12/20Version history — 4 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesspryker/sales-order-amendment-extension
ecosystemspackagist
any_deprecatedno
min_days_since_publish399

Engineering Quality

Are baseline engineering and documentation practices in place?

57Moderate · 19% of overall

Engineering practices

58Moderate
How it's scored
24/24CI workflows — 1 workflow(s)
0/24Tests present
16/16Linter config — phpstan.neon
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsno
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 site — https://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?

31At Risk · 16% of overall

Security posture

31At Risk
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/6 approved changesets -- score normalized to 0
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
2.2/2.5License — license file detected
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — no SAST tool detected
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_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate3.1
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.

17Critical · 4% of overall

Agent context & guidance

1Critical
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no 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.

Verify loop (build / test / typecheck)

15Critical
How it's scored
0/18One-command bootstrap
0/22Automated tests
11/11Lint / format config — phpstan.neon
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no data
0/8Automated maintenance — no data
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
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.

Code legibility for models

55Moderate
How it's scored
0/45Type-checkable code — PHP without a type-check config
55/55Manageable file sizes — 0/13 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes1,610
source_files_sampled13
oversized_source_files0

Key facts

0GitHub stars
5contributors
0commits, last 12 months
315days since last push
4releases
2bus factor
0open issues
Packagistpackage ecosystems

Data collection warnings

  • No resolved dependencies carried a version and a supported ecosystem

More detail

OpenSSF Scorecard 3.1 / 10
3.1aggregate

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-13 21:31 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/6 approved changesets -- score normalized to 0
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
9Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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 1
RegistryPackageVersion constraintManifest
Packagistspryker/transfer^3.27.0composer.json
All dependencies 3

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

RegistryPackageVersionRelation
Packagistspryker/transfer—direct
Packagistphp—indirect
Packagistspryker/code-sniffer—indirect
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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with spryker/sales-order-amendment-extension. Read them side by side →

99taskforcesh/bullmqBullMQ - Message Queue and Batch processing for NodeJS, Python, .NET, Elixir, Rust and PHP based on Redis or PostgreSQLExceptional99stripe/stripe-phpPHP library for the Stripe API. Exceptional99WordPress/gutenbergThe Block Editor project for WordPress and beyond. Plugin is available from the official repository.Exceptional99grpc/grpcC++ based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)Exceptional98swagger-api/swagger-uiSwagger UI is a collection of HTML, JavaScript, and CSS assets that dynamically generate beautiful documentation from a Swagger-compliant API.Exceptional98Sylius/SyliusHeadless open-source eCommerce platform on top of PHP/Symfony/API PlatformExceptional

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.31.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — Packagist.