Maintenance has gone quiet recently, and the project has one registry maintainer with no security policy or scanning. Its long release history, clear documentation, licensing, and non-archived repository provide useful support.
58%
Total Score
50
100
88
75
Only one account has registry publishing access. A single maintainer is not inherently unsafe, but it increases continuity risk alongside the observed lack of recent activity.
The package has 151 releases over more than eight years, but none in the last 12 months despite a previously regular median interval of about 5 days. This indicates a substantial recent slowdown.
The repository recorded zero commits and zero active maintainers in the last 3 months. Combined with no releases in the last 12 months, this is evidence of recently quiet maintenance.
Composer build tooling is present, but no security scanning tools are configured. That weakens the project's release and dependency oversight.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap for a package used in websites.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
neos/neos Version ^7.0 || ^8.0 || ^8.1 | — | — |
neos/nodetypes Version * | — | — |
twbs/bootstrap Version ^5.2 | — | — |
shel/neos-colorpicker Version ^1.4 | — | — |
neosrulez/countrydatasource Version ^1.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.