spryker/dynamic-entity-extension
Documentation, licensing, and contributor spread are solid, with no deprecation or install scripts. The workflow leaves two of four actions unpinned, and the project has no security policy or automated security scanning.
79%
Total Score
100
86
75
Health Score Breakdown
The package has had only one registry release, about 3 years ago, which limits release-history evidence and raises a maintenance concern. Recent repository commits partly offset the lack of registry releases.
Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency and hygiene gap, not evidence of abandonment.
The repository has no security policy, leaving vulnerability reporting and response expectations unspecified. This lowers transparency but does not by itself indicate an unsafe release.
The single workflow was fully analyzed with no injection or high-severity findings, but 2 of 4 action references are unpinned. The absence of a top-level permissions block is acceptable on its own.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 spryker/transfer Version ^3.27.0 | — | — |
Weekly Downloads
Info
- Last Published
- 3 years ago
- Created
- 3 years ago
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.