spryker/merchant-file

Registry deprecationdanger

Packagist marks the entire package as abandoned, with no replacement specified. This is a severe adoption risk even though the repository remains available.

Release historydanger

This is the only release, published about 14 months ago, with no releases in the last 12 months. That provides little evidence of ongoing delivery.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last 3 months. Combined with the single-release history, this indicates likely abandonment.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap, not a standalone adoption blocker.

Security policycaution

The repository has no security policy. That weakens vulnerability-reporting transparency, although it is secondary to the package's abandonment signals.