AclEntity module
91%
Total Score
healthy
Recent releases, active contributors, and organization backing show strong maintenance with only minor workflow and security-policy gaps.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a minor repository-hygiene gap, not evidence of abandonment by itself.
No repository security policy was found. This weakens the documented vulnerability-reporting path, although the active organization-backed project and recent maintenance partly compensate.
The single workflow was fully audited with no findings, no untrusted checkouts, and no script-injection risks; two of four action references are unpinned, which is a minor reproducibility and supply-chain hygiene gap. No top-level permissions block is acceptable here because the workflow has no write permissions or untrusted trigger.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/acl Version ^3.8.0 | — | — |
spryker/user Version ^3.0.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/symfony Version ^3.0.0 | — | — |
spryker/transfer Version ^3.27.0 | — | — |
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.