spryker/agent

This release appears healthy and suitable to depend on: it has a long release history, a current stable version, recent publishing activity, an active non-archived organization-owned repository, six active contributors in the last 3 months, and clear artifact and repository structure with tests, changelog, license, and CI workflow coverage. The main reservations are the absence of a repository security policy, missing explicit top-level workflow token permissions, and no detected security-scanning tooling; these are transparency and defense-in-depth gaps rather than evidence of abandonment. Repository popularity is low, but that is weak supporting evidence and is offset by recent releases and distributed organizational maintenance.

Latest 1.11.0Packagist

Health Score Breakdown

Repo toolingcaution

The repository uses Composer build tooling, but no security-scanning tools were detected; this is a defense-in-depth gap, though it is partly compensated by the presence of CI and other repository hygiene signals.

Security policycaution

No SECURITY.md or equivalent security policy was found, reducing vulnerability-reporting transparency and maintainer response guidance.

Token permissionscaution

The only workflow lacks top-level token permissions, and no read-only permissions declaration was detected; this weakens least-privilege clarity even though no top-level write permissions were found.

View all 19 health checks

Vulnerabilities

We didn't find any vulnerabilities for this package.

Direct Dependencies

Dependency	Last Release	Score
spryker/user Version ^3.32.0	—	—
spryker/kernel Version ^3.30.0	—	—
spryker/propel Version ^3.46.0	—	—
spryker/session Version ^3.2.0 || ^4.0.0	—	—
spryker/customer Version ^7.81.0	—	—

View All 12 Dependencies