The package is small and clearly documented, with a matching repository and a recent release. Its low release cadence, single recent contributor, and absent security policy leave limited evidence of long-term resilience.
70%
Total Score
67
100
86
75
The package has only 5 releases since August 2021, with a median interval of about 357 days and one release in the last 12 months. The recent v2.3 release shows it is not abandoned, but maintenance is infrequent.
All recent commits came from one contributor, so maintenance depends heavily on a single person. Organization ownership provides some handoff potential, but no second active contributor is shown.
There was one commit by one active maintainer in the last 3 months, including the recent release. This demonstrates current activity but provides only limited evidence of sustained maintenance capacity.
Composer build tooling is present, while no security scanning tools were detected. The missing scanning tooling is a modest hygiene gap, not a standalone dependency-blocking risk.
The repository has no security policy, leaving reporting and disclosure expectations undocumented. This is a transparency gap rather than evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^9.0 || ^10.0 || ^11.0 || ^12.0 || ^13.0 | — | — |
illuminate/filesystem Version ^9.0 || ^10.0 || ^11.0 || ^12.0 || ^13.0 | — | — |
biigle/flysystem-elements Version ^2.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.