Get the remote origin URL of a Git repository
62%
Total Score
50
100
89
88
50
No build attestation or trusted-publisher provenance is available, leaving publication origin less transparent. This is a supply-chain hygiene gap rather than evidence that the release is unsafe.
Only one registry publishing account is listed, which is a thin publishing base. The linked repository identifies the same individual owner, but recent commit activity is still absent.
The repository is owned by an individual rather than an organization, so there is no organizational backing to offset the thin maintainer base.
The package has 0 releases in the last 12 months, and its latest registry release was about 5 years ago. That weakens evidence of ongoing maintenance, although the long release history shows it is established.
The repository recorded 0 commits and 0 active maintainers in the last 3 months. This indicates limited recent development activity, despite the repository not being archived.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
gitconfiglocal Version ^2.1.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.