spryker/companies-rest-api

This release appears healthy and suitable for dependency use: it has a long release history dating to 2019, six releases in the last 12 months, stable versioning, no registry deprecation, an active non-archived organization-owned repository, recent commits from five maintainers, and complete package scaffolding including tests, changelog, license, and CI configuration. The main reservations are the absence of a repository security policy and explicit top-level GitHub Actions token permissions, plus no automated security scanning tools; these are transparency and workflow-hygiene gaps rather than evidence of abandonment. Repository popularity is low, but that is appropriately outweighed by the demonstrated maintenance activity and organizational backing.

Latest 1.7.2Packagist

Health Score Breakdown

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected; this is a modest security-process gap without evidence of poor build provenance.

Security policycaution

The repository has no security policy, reducing transparency about vulnerability reporting and response procedures; this is a genuine but limited governance gap.

Token permissionscaution

The only workflow lacks top-level token permissions, so least-privilege configuration is not explicitly documented; no top-level write permissions were detected, making this a hygiene caution rather than a severe workflow risk.

View all 19 health checks

Vulnerabilities

We didn't find any vulnerabilities for this package.

Direct Dependencies

Dependency	Last Release	Score
spryker/kernel Version ^3.30.0	—	—
spryker/company Version ^1.9.0	—	—
spryker/symfony Version ^3.0.0	—	—
spryker/transfer Version ^3.42.0	—	—
spryker/uuid-behavior Version ^1.0.0	—	—

View All 8 Dependencies