Tool to interactively populate a `.env` file based on an `.env.example` file whenever Composer installs or updates.
60%
Total Score
67
100
88
75
The repository is owned by an individual user rather than an organization, so the project has limited visible institutional backing. This matters more alongside the lack of recent activity.
The package has had no releases in the last 12 months, and its latest release was over five years ago. That materially raises maintenance and abandonment risk.
There were no commits and no active maintainers in the last three months, consistent with the release history and indicating a substantial maintenance gap.
Composer build tooling is present, but no security scanning tools were detected. For a small package this is a modest transparency gap rather than a severe risk.
The repository has no security policy, leaving reporting and disclosure expectations undocumented. This lowers transparency but is not by itself evidence that the release is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
m1/env 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.