The MIT declaration, matching repository, and lack of install-time scripts provide basic transparency and reduce installation risk. However, the package contains only three files and has no tests, security policy, or scanning, leaving little evidence of ongoing maintenance or review capacity.
38%
Total Score
0
71
67
The package has had only two releases, both in May 2016, with no release in roughly 10 years. This is strong evidence of abandonment for a dependency expected to receive maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity since 2016.
The artifact and repository each contain only README.md, composer.json, and scr/r.md. This may be intentionally small, but it provides very little implementation or documentation evidence for a dependency.
A README is present, but it contains only eight characters, and the project has no tests or changelog. Missing tests and changelog are normal in published artifacts, while the extremely limited README weakens consumer transparency.
Composer is used for the build, but no security-scanning tooling is present. This is a modest hygiene concern rather than evidence that the release is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ~5.0 | — | — |
illuminate/filesystem Version ~5.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.