technically/dependency-resolver
Clear documentation, tests, release notes, and a recent stable release support adoption. The small maintainer base and absent security scanning leave less evidence for long-term resilience, despite organization backing.
72%
Total Score
67
100
93
67
Health Score Breakdown
Only one registry account has publishing access. The repository is organization-owned, which provides some backing, but the observed publishing base remains narrow.
The repository recorded zero commits and zero active maintainers during the last three months, which weakens evidence of ongoing maintenance even though a recent release exists.
The project uses Make and Composer, but no security scanning tools were detected, leaving a gap in repository hygiene and vulnerability detection.
The repository has no security policy, so users are given no documented process for reporting or handling vulnerabilities.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, or audit findings. However, both of its two action references are unpinned, reducing build reproducibility and supply-chain transparency.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Ivan Voskoboinyk |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 psr/container Version ^2.0 | — | — |
technically/null-container Version ^2.0 | — | — |
technically/callable-reflection Version ^0.5.0 | — | — |
Weekly Downloads
Info
- Last Published
- 4 months 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.