The 0.1.1 version is early-stage, and the project has no published security policy. Its license, release notes, and Dependabot setup provide useful transparency, but repository identity and workflow practices need attention.
55%
Total Score
50
75
75
The package has two releases, with the latest published about five months ago and a median interval of about five days. This shows an initial release cadence but limited history.
The repository recorded zero commits and zero active maintainers in the last three months. For a package with only two releases, this is a meaningful maintenance concern, though it does not yet prove abandonment.
The repository name does not match the package name and its README does not mention the package, so the package-to-source relationship is less transparent. Organization ownership provides context but does not resolve that missing link.
The repository has no security policy, leaving no documented path for reporting vulnerabilities. This is a transparency gap for a dependency, but not severe on its own.
Version 0.1.1 is not a stable major release, so its API and behavior may still change. It is not marked as a prerelease, which provides some compensation.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
neos/form Version * | — | — |
neos/neos Version >=8.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.