The MIT license, README, changelog, and small dependency set make it straightforward to inspect and integrate. Treat future fixes as uncertain and avoid relying on it for a new deployment workflow.
38%
Total Score
25
100
75
75
The package has only two releases, both published in February 2017, with none in the last nine years. That is strong evidence of abandonment for a deployment tool.
The repository recorded zero commits and zero active maintainers in the last three months, while its last push was in 2017. The linked repository is not archived, but there is no observed recent maintenance.
One registry maintainer is consistent with a user-owned project, but it leaves little apparent maintenance capacity when combined with the long release and commit inactivity.
The repository has no security policy. This is a modest transparency gap, though it is secondary to the much stronger evidence of long-term inactivity.
The latest version is v0.0.2 and is not a stable major release, indicating a very early maturity level. The absence of prerelease labeling does not offset the low version maturity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravelcollective/remote Version ^5.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.