spryker/shipment-type

This release appears suitable for dependency use: it is stable, not deprecated, backed by an active non-archived organization-owned repository, and has strong repository structure with tests, changelog, CI tooling, and balanced recent contributor activity. The main concerns are that only one release was published in the last 12 months and the repository lacks a security policy and explicit top-level workflow token permissions. These are meaningful hygiene gaps, but they do not outweigh the evidence of current maintenance, licensing, package transparency, and low-risk workflow configuration.

Latest 1.3.0

Packagist

86%

Total Score

Maintainer Stability

100

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has existed for 1221 days with 13 releases and a median release interval of about 25 days, but only one release occurred in the last 12 months. The recent cadence warrants monitoring, though it does not by itself establish abandonment.

Repo tooling

The repository uses Composer build tooling, but no security-scanning tools were detected. Build support is present while automated security hygiene is limited.

Security policy

No repository security policy was found. This reduces vulnerability-reporting transparency, although it is a process gap rather than evidence of unsafe code.

Token permissions

The one workflow lacks top-level token permissions, while no top-level write permissions were detected. Explicit least-privilege declarations would improve hardening, but the absence of write declarations limits the observed risk.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

No maintainer information available.

Direct Dependencies

Dependency	Last Release	Score
spryker/store Version ^1.12.0	—	—
spryker/kernel Version ^3.30.0	—	—
spryker/shipment Version ^8.0.0	—	—
spryker/transfer Version ^3.27.0	—	—
spryker/propel-orm Version ^1.6.0	—	—