This simple template automatically resolves file paths according to the Neos best practises.
42%
Total Score
unhealthy
Risky: no release or commit activity since June 2018, with minimal repository adoption.
The latest of only two releases was published in June 2018, and there have been no releases in the last 12 months. This is strong evidence of abandonment risk for a package intended as an application dependency.
There were zero commits and zero active maintainers in the last three months, consistent with the repository's last push in June 2018. This materially increases abandonment risk.
The repository has zero stars and forks and only two watchers. Popularity is supporting evidence rather than a verdict, but these figures provide little evidence of broad community validation.
Composer build tooling is present, but no security scanning tools are configured. For a small package this is a hygiene gap, though it is less important than the long-standing inactivity.
The repository has no security policy. This weakens vulnerability-reporting transparency, but it is a secondary concern for a small, inactive package.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
neos/neos Version ^3.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.