Adoption is very limited, and the repository has no security scanning or published security policy. The MIT license, focused dependency set, clear README, and matching source repository provide useful transparency, but do not offset the long abandonment risk.
40%
Total Score
0
75
75
The latest release was in October 2014, and there have been no releases in roughly 11 years and 11 months. This is strong evidence of abandonment for a dependency that may need compatibility or security fixes.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history and indicating no current maintenance capacity.
The repository has only 1 star, 0 forks, and 3 watchers, providing little evidence of a community that could help maintain or repair the package.
Composer is used for the build, which fits the package ecosystem, but no security scanning tools are present. The missing scanning is a modest hygiene concern rather than evidence of malicious behavior.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a secondary transparency gap alongside the much stronger inactivity concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
typo3/flow Version * | — | — |
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.