Testing, licensing, and a small runtime dependency set support routine adoption. Maintenance has been quiet, and six workflow actions are unpinned, reducing confidence in ongoing care and reproducible automation.
58%
Total Score
67
100
75
75
Only two releases exist, with the latest about 14 months ago and none in the last 12 months. This is meaningful evidence of a slow or paused release cadence, although the repository is not archived.
The repository recorded no commits and no active maintainers in the last three months. The recent release and non-archived status provide some evidence of prior maintenance, but not current activity.
There were no new or closed issues or pull requests in the last month. With no recent commits as well, this suggests limited current project activity, though the lack of open work is not itself harmful.
The repository has zero stars and forks and one watcher, providing little community validation or outside maintenance capacity. Low popularity is supporting evidence only and does not outweigh the package's organization backing by itself.
The repository has no security policy. That weakens vulnerability-reporting transparency, though the package is small and no direct security defect is shown.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
imedge/config Version >=0.3 | — | — |
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.