spryker/api

Healthy and suitable to adopt, with strong repository hygiene and active organizational maintenance. The main caveats are only one release in the last 12 months and limited security-process visibility, including no security policy or automated security scanning.

Latest 0.4.5

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has existed since May 2017 with 22 releases, but only one release was published in the last 12 months. The recent cadence is a maintenance caveat, though the latest release was published very recently.

Repo issue activity

There were no new issues or pull requests in the last month and no pull requests were merged, which limits evidence of current issue-handling activity; the open-issues count is unavailable.

Repo tooling

The repository uses Composer for builds, but no security scanning tools were detected. Build tooling is present, while automated security coverage is a transparency gap.

Security policy

No repository security policy was found, reducing transparency about vulnerability reporting and response procedures.

Token permissions

The only workflow lacks top-level token permissions. Although no write permissions were explicitly observed, declaring least-privilege permissions would provide clearer CI security boundaries.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

No maintainer information available.

Direct Dependencies

Dependency	Last Release	Score
spryker/log Version ^3.0.0	—	—
spryker/kernel Version ^3.52.0	—	—
spryker/symfony Version ^3.5.0	—	—
spryker/transfer Version ^3.25.0	—	—
spryker/util-text Version ^1.1.1	—	—