The README and MIT license make the example understandable and legally usable. Its small dependency set and matching repository help, but it lacks a security policy and automated security scanning.
38%
Total Score
0
100
79
67
This package has only one release, published over 11 years ago, with no releases in the last 12 months. That provides strong evidence of abandonment for a dependency intended for ongoing use.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with its last push in March 2015. No provided signal shows current maintenance capacity.
The package runs post-install and post-update Composer scripts. These add install-time execution risk and deserve review, though this signal alone does not establish that the release is unsafe.
Composer is used for builds, but the repository reports no security scanning tools. This is a modest transparency and maintenance gap, especially for a package with install scripts.
The repository has no security policy. For an old example application this is a hygiene gap rather than evidence of a vulnerability, but it reduces transparency for reporting issues.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
typo3/flow Version 2.3.* | — | — |
typo3/welcome Version 2.3.* | — | — |
symfony/serializer Version ~2.6 | — | — |
doctrine/migrations Version @dev | — | — |
helmich/flow-resttools Version dev-master | — | — |
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.