The package is small and focused, with one runtime dependency, a clear README, stable MIT licensing, and release notes for this version. The repository has been quiet for about three years, and its name and README do not clearly identify this package.
56%
Total Score
75
100
86
75
The package has had no release in about three years and none in the last 12 months, which lowers confidence in ongoing maintenance. Its five-release history shows it was previously maintained, so this is caution rather than a severe abandonment verdict.
The repository recorded no commits and no active maintainers in the last three months, consistent with the long release gap. The repository is not archived, which partly offsets the concern but does not show current maintenance.
The repository name does not match the package name and its README does not mention the package, so the source relationship is less transparent than expected. The linked repository is organization-owned, which provides some backing but does not resolve the identification gap.
The repository has no security policy. This is a transparency and reporting gap, though the package's small, focused scope keeps it from being a severe health risk on its own.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
neos/flow Version ^7.0 || ^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.