Its README, tests, release notes, and license make the package transparent to consumers. One publisher, no security policy, and unpinned workflow actions add smaller maintenance and hygiene concerns.
65%
Total Score
50
100
88
67
Only one registry account has publishing access. The linked repository is user-owned rather than organization-owned, so there is no provided organizational backing to compensate for the narrow publisher base.
The repository is owned by the same individual associated with the package namespace, which supports a consistent ownership story. It is not organization-backed, so the package appears dependent on an individual maintainer.
The package has 11 releases since November 2019, but no releases in the last 12 months despite a latest release in June 2025. This indicates a meaningful slowdown, though the release history is established rather than abandoned.
There were no commits and no active maintainers in the last three months. Combined with no releases in the last 12 months, this is evidence of currently quiet maintenance.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and hygiene gap rather than a severe dependency risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
neos/neos Version ^9.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.