pierreminiggio/config-provider
The one-person project has no security policy or scanning, while the two-file repository provides little evidence of ongoing support. Its stable version and minimal dependency surface reduce complexity but do not offset the long inactivity.
38%
Total Score
50
100
71
75
Health Score Breakdown
Only one release exists, published roughly 5 years ago, with no releases in the last 12 months. That strongly raises abandonment risk for a dependency.
No declared license, license file, or repository license file was detected. This creates a real legal and transparency concern for adoption.
The repository recorded no commits and no active maintainers in the last 3 months, consistent with the package's roughly 5-year release gap and limited maintenance evidence.
The repository name does not match the package name, and no README mention was available. That leaves some uncertainty about package-to-repository alignment, although a subpackage naming difference can be normal.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. The absence of security scanning in the repository tooling provides no compensating evidence.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Pierre MINIGGIO |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 5 years ago
- Created
- 5 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.