A clear README, matching repository, and explicit licensing improve transparency. The short release history and absent tests and security policy leave maintenance confidence limited.
55%
Total Score
50
79
75
The release includes a LICENSE file and the repository also has one, so licensing is not absent. The manifest declares GPL-3.0+ while the artifact license text was recognized as GPL-3.0, creating a minor declaration mismatch.
The package has only two releases, both on January 27, 2026, with no later release activity over roughly eight months. This is a meaningful maintenance concern for a package still early in its lifecycle.
The repository recorded zero commits and zero active maintainers during the last three months. That lack of recent development lowers confidence that bugs and compatibility changes will be addressed promptly.
Composer build tooling is present, but no security scanning tools are reported. This modestly reduces assurance around ongoing project hygiene.
The linked repository has no security policy, leaving no documented path for reporting vulnerabilities or communicating security handling. This is a transparency and maintenance gap, though it does not by itself make the release unfit.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
neos/form Version ^5.0 || ^6.0 | — | — |
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.