spryker/shipment-types-rest-api

This release appears healthy and suitable to depend on: it has a stable release history, ongoing recent releases, an active non-archived organization-owned repository, five active contributors in the last three months, comprehensive source and test scaffolding, and no install-time lifecycle scripts or dangerous workflow patterns. The main reservations are the absence of a repository security policy, undeclared top-level GitHub Actions token permissions, no automated security-scanning tooling, and very low repository popularity; these are hygiene concerns rather than evidence of abandonment, especially given the recent release and commit activity.

Latest 1.3.3Packagist

Health Score Breakdown

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected, leaving a moderate repository security-hygiene gap.

Security policycaution

The repository has no SECURITY.md or other detected security policy, reducing transparency for vulnerability reporting and coordinated response.

Token permissionscaution

The sole workflow lacks top-level token permissions, so its effective permission posture is not explicitly constrained; no top-level write permission was detected, but the omission remains a hygiene concern.

View all 19 health checks

Vulnerabilities

We didn't find any vulnerabilities for this package.

Direct Dependencies

Dependency	Last Release	Score
spryker/store Version ^1.19.0	—	—
spryker/kernel Version ^3.66.0	—	—
spryker/symfony Version ^3.0.0	—	—
spryker/shipment Version ^8.16.0	—	—
spryker/transfer Version ^3.42.0	—	—

View All 11 Dependencies