dashifen/wp-debugging
The package is small and clearly tied to its repository, with one runtime dependency and a stable 1.0.2 release. Its MIT license file conflicts with the proprietary manifest, and the repository has no security policy or scanning tools.
57%
Total Score
50
100
79
83
Health Score Breakdown
The artifact includes an MIT license file, which provides licensing evidence, but the manifest declares the package proprietary. That mismatch creates avoidable legal and transparency uncertainty.
The latest release was in September 2023, with no releases in nearly three years and only three releases overall. This indicates a slow maintenance cadence for a package that may still be usable but is not actively evolving.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long gap since the last release. The repository is not archived, but current maintenance activity is absent.
Composer build tooling is present, but no security-scanning tools were detected. This is a minor supply-chain hygiene gap rather than evidence that the package is unsafe.
No security policy is present in the linked repository. This is a modest transparency gap for a package with no other observed security process.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 David Dashifen Kees |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 dashifen/debugging Version ^1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 3 years ago
- Created
- 6 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.