dnj/windows-isomaker
Tests and release notes provide some evidence of a deliberate release, and organization ownership adds limited continuity. The absent security tooling leaves maintenance assurance thin.
42%
Total Score
50
100
67
75
Health Score Breakdown
The package has only two releases, with the latest published about five years ago and none in the last 12 months. This strongly raises abandonment risk despite the short two-day initial release interval.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving current maintenance capacity unproven.
The artifact has tests, the repository has tests, and this version has GitHub release notes, which provide useful evidence of intentional development. The missing README is a minor consumer-documentation gap for a library.
Composer build tooling is present, but no security scanning tools were detected. That leaves a modest gap in ongoing maintenance assurance.
No repository security policy was found, reducing transparency about how vulnerabilities would be reported and handled.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 psr/log Version ^1|^2|^3 | — | — |
dnj/isomaker Version ^1.1 | — | — |
dnj/autounattend Version ^1.0 | — | — |
dnj/tmp-filesystem Version ^1.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.