mikp/wn-sanctum-tokens-plugin
The package is licensed, documented, and its repository matches the package, which supports straightforward use. Its single-maintainer setup and lack of security policy add ongoing ownership risk.
39%
Total Score
50
100
75
83
Health Score Breakdown
This is the only release, published over four years ago, with no releases in the last 12 months. That strongly indicates abandonment risk for a dependency.
Only one registry maintainer is listed. For a user-owned project this leaves limited visible publishing redundancy and increases continuity risk.
The repository is owned by the same individual namespace as the package rather than an organization, so the single-maintainer concern is not offset by visible organizational backing.
The repository had zero commits and zero active maintainers in the last three months, consistent with the long release gap and strengthening the abandonment concern.
Composer build tooling is present, but no security-scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe risk.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 mik-p |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 treeware/plant Version ^0.1.0 | — | — |
laravel/sanctum Version ^2.12 | — | — |
composer/installers Version ~1.0 | — | — |
winter/wn-user-plugin Version ^2.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.