Set a .env file variable from the command line
68%
Total Score
caution
Usable with caveats: recent releases are offset by three months without repository activity.
Only one registry account has publish access. The matching user-owned repository and observed release activity provide some compensation, but the publishing base remains narrow.
The repository recorded zero commits and zero active maintainers in the last three months. The recent release partly offsets this, but the current maintenance signal is weak.
There are no open issues and one open pull request, but no issues or pull requests were merged in the last month. This is limited evidence of current project interaction.
Composer is used as the build tool, but no security scanning tools were detected. The missing scanning is a modest transparency and hygiene gap.
The repository has no security policy. For a small command package this is a limited gap, but it leaves vulnerability-reporting expectations unclear.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/console Version ^12.0|^13.0 | — | — |
illuminate/support Version ^12.0|^13.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.