Manage Magento 2 Content Security Policy whitelist hosts from the admin.
68%
Total Score
caution
A first-ever release with no follow-up commits leaves maintenance maturity unproven.
Only one registry account has publishing access. That is a limited publishing base, although the repository provides additional evidence of project structure and ownership.
The repository is owned by an individual user rather than an organization, so the single registry maintainer does not benefit from clear organizational backing.
This is the package's first release, published 0 days ago, so there is no release history or cadence demonstrating sustained maintenance.
The repository has 0 commits and 0 active maintainers in the last 3 months, consistent with a newly published project but leaving ongoing maintenance unproven.
The repository has zero stars, forks, and watchers. Given that it was created on the release date, this is limited maturity evidence rather than a severe concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
magento/framework Version >=103.0.6 | — | — |
magento/module-csp Version >=100.4 | — | — |
magento/module-config Version >=101.2 | — | — |
magento/module-backend Version >=102.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.