sirix/container-resolver
Its small public footprint and single registry maintainer limit independent assurance. The workflow uses two unpinned actions, but repository tests, release notes, security scanning, and recent publishing support adoption.
82%
Total Score
50
100
89
75
Health Score Breakdown
Only one registry account has publish access, limiting publishing redundancy. The repository's recent release and test evidence provide some compensation, but not independent maintainer depth.
The repository is owned by an individual account rather than an organization, so the single registry maintainer does not benefit from visible organizational backing.
Five releases in 112 days, with a median interval of about 2 days, show active early development, though the project is still young and its longer-term maintenance record is limited.
The repository has zero stars and forks and one watcher, so there is little independent adoption evidence. Popularity is supporting evidence rather than a health verdict, and the package has other positive signals.
No repository security policy was found, leaving vulnerability reporting guidance undocumented. This is a transparency gap, not evidence of unsafe code.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Sirix |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 psr/container Version ^1.0 || ^2.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 month ago
- Created
- 3 months 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.