Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-17 17:39 UTC

spryker / asset-storage

[READ ONLY] Subtree split of the AssetStorage module.

PHPCustom license★ 0 stars⑂ 0 forkssince Apr 2022View on GitHub ↗

spryker/asset-storage holds a health index of 54 out of 100, placing it in the Moderate band. It scores highest on Sustainability & Governance (86/100) and lowest on Security (1/100). It was last updated today. 6 contributors account for most of its recent work.

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

54
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 53 is calibrated to 54 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/asset-storage1.3.015,8646378 days ago

Metrics by category

Vitality

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

50Moderate · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
2.1/36Commit cadence3/52 weeks with commits
5.4/18Commit volume3 commits in the last year
0/10OpenSSF Scorecard: Maintainedno data
Inputs used
commits_last_year3
human_commit_share1
days_since_last_push0
active_weeks_last_year3
How it's scored
27/27Ships releases6 releases published
7.2/36Release recencylatest release 378 days ago
12.6/27Release cadencea release every ~241.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count6
latest_release_tag1.3.0
releases_from_tagsno
days_since_latest_release378
mean_days_between_releases241.4

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

41Weak · 17% of overall
How it's scored
0/60Stars0 stars
0/25Forks0 forks
3.3/15Watchers5 watchers
Inputs used
forks0
stars0
watchers5
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
56/80Monthly downloads15,864 downloads/month across packagist
2/20Registry dependents1 packages depend on it
Inputs used
packagesspryker/asset-storage
dependents1
ecosystemspackagist
total_downloads1,009,266
monthly_downloads15,864
unverified_packages_excluded

Sustainability & Governance

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

86Excellent · 23% of overall
How it's scored
48.6/54Bus factor6 contributor(s) cover half of all commits
18.3/22.5Commit distributiontop contributor authored 18% of commits
13.5/13.5Contributor breadth17 contributors
0/10OpenSSF Scorecard: Contributorsno data
Inputs used
bus_factor6
contributors_sampled17
top_contributor_share0.185
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
14.8/25Owner reach113 followers of spryker
25/25Track record1,334 public repos, account ~11 yr old
Inputs used
followers113
owner_typeOrganization
is_verified
owner_loginspryker
public_repos1,334
account_age_days4,267
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on packagist
14/35Publish recencylatest publish 378 days ago
20/20Version history6 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesspryker/asset-storage
ecosystemspackagist
any_deprecatedno
min_days_since_publish378

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

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?

1Critical · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfilespublished library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles
manifestscomposer.json
has_codeql_workflowno
has_security_policyno
has_dependabot_configno
Excluded from scoring (no data or not applicable): Dependency lockfiles. 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.

38Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
31.3/40Legible commit history17 of 29 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.586
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 29
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
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/54 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes11,238
source_files_sampled54
oversized_source_files0

Key facts

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

Data collection warnings

  • No resolved dependencies carried a version and a supported ecosystem
  • OpenSSF Scorecard did not return a usable result (Skipping github.com/spryker/asset-storage: run: internal error: ListCommits:error during graphqlHandler.setup: internal error: githubv4.Query: non-200 OK status code: 503 Service Unavailable body: "{\"message\": \"No server is currently available to service your request. Sorry about that. Please try resubmitting your request and contact us if the problem persists.\"}\r\n"); skipping Scorecard checks

More detail

Direct dependencies 10
RegistryPackageVersion constraintManifest
Packagistspryker/asset^1.4.0composer.json
Packagistspryker/kernel^3.30.0composer.json
Packagistspryker/propel-orm^1.3.0composer.json
Packagistspryker/publisher-extension^1.0.0composer.json
Packagistspryker/storage^3.0.0composer.json
Packagistspryker/store^1.0.0composer.json
Packagistspryker/synchronization^1.0.0composer.json
Packagistspryker/synchronization-behavior^1.0.0composer.json
Packagistspryker/synchronization-extension^1.1.0composer.json
Packagistspryker/transfer^3.27.0composer.json
All dependencies 18

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

RegistryPackageVersionRelation
Packagistspryker/assetdirect
Packagistspryker/kerneldirect
Packagistspryker/propel-ormdirect
Packagistspryker/publisher-extensiondirect
Packagistspryker/storagedirect
Packagistspryker/storedirect
Packagistspryker/synchronizationdirect
Packagistspryker/synchronization-behaviordirect
Packagistspryker/synchronization-extensiondirect
Packagistspryker/transferdirect
Packagistphpindirect
Packagistspryker/code-snifferindirect
Packagistspryker/eventindirect
Packagistspryker/event-behaviorindirect
Packagistspryker/propelindirect
Packagistspryker/publisherindirect
Packagistspryker/queueindirect
Packagistspryker/testifyindirect
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.31.0 — full methodology · metrics wiki.

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