spryker/dynamic-entity

This release appears healthy and suitable for dependency use: it has a stable release profile, regular recent publishing, an active non-archived organization-backed repository, five active contributors in the last three months, comprehensive source and artifact tests, a changelog, and no install-time lifecycle scripts. The main reservations are the absence of a repository security policy and undeclared top-level GitHub Actions token permissions, plus no configured security-scanning tool; these are transparency and CI-hardening gaps rather than evidence of abandonment. The proprietary license is explicitly declared and accompanied by a LICENSE file, so licensing is clear, although downstream users should verify that its terms fit their project.

Latest 1.21.1Packagist

Health Score Breakdown

Repo toolingcaution

The repository uses Composer build tooling, but no security-scanning tools were detected. The missing scanning automation is a security-process gap, though it is partly offset by the active organization-backed development workflow.

Security policycaution

No repository security policy was found. This reduces vulnerability-reporting transparency and is a genuine, though not severe, supply-chain maintenance gap.

Token permissionscaution

The sole workflow has no top-level permissions declaration. Although no top-level write permissions were detected, explicitly declaring least-privilege permissions would provide stronger CI hardening and transparency.

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/symfony Version ^3.0.0	—	—
spryker/transfer Version ^3.27.0	—	—
spryker/propel-orm Version ^1.6.0	—	—
spryker/util-encoding Version ^2.0.0	—	—

View All 7 Dependencies