dnj/image
The missing README and security policy make integration and security reporting less transparent. MIT licensing, a stable release, organization backing, and a small runtime dependency set provide useful positives, but they do not offset the limited project evidence.
39%
Total Score
50
100
75
50
Health Score Breakdown
This package has only one release, published about 4 years 8 months ago, with no releases in the last 12 months. That is strong evidence of limited ongoing maintenance.
The repository has recorded no commits and no active maintainers in the last 3 months, consistent with the long release gap and increasing abandonment risk.
The artifact has no README, which makes a consumer-facing image library harder to understand and integrate. Tests and a changelog are not expected in the published artifact, while release notes for this version are present.
Composer build tooling is present, but no security-scanning tool was detected. That leaves less visible evidence of automated security checks.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency gap, though it is not by itself evidence of unsafe code.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 dnj/tmp-filesystem Version ^1.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 4 years ago
- Created
- 4 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.