Generate a unique enough deployment identifier
62%
Total Score
caution
Usable with caveats: long release gaps, no license, and unpinned CI actions limit confidence.
No declared license or license file was detected in the package or repository, leaving the terms for reuse unclear.
Only two releases span roughly four years, with no release in the last 12 months; this indicates a low-maintenance project, though the package may be intentionally stable.
There were no commits or active maintainers in the last three months, consistent with the long release gap and reducing confidence in ongoing maintenance.
Composer build tooling is present, but no security scanning tooling was detected; this is a modest transparency and maintenance gap for a small package.
The repository has no security policy, reducing clarity about how vulnerabilities should be reported, although this is not severe for a small utility by itself.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
eiriksm/gitinfo Version ^2.0||^3.0||^4.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.