pkc/role-permission
Usable with caveats: the package is licensed, documented, non-deprecated, and its repository matches the package. It is very new, all three releases arrived on one day, and there has been no commit activity since then, with no security policy or scanning; treat ongoing maintenance as uncertain.
52%
Total Score
33
100
83
88
Health Score Breakdown
There were zero commits and zero active maintainers in the last 3 months. For a package this young, that is strong evidence that ongoing maintenance has not yet been demonstrated.
Only one registry account has publish access. The linked project is user-owned rather than organization-backed, so this represents a meaningful continuity risk if that maintainer becomes inactive.
The registry namespace and repository owner differ, and the repository owner is an individual rather than an organization. This provides limited backing beyond the single publisher account.
The package is 247 days old but all three releases were published within roughly 8 hours, leaving little evidence of sustained release maintenance after its initial launch.
The repository has zero stars, forks, and watchers, providing no community adoption or external visibility to compensate for its limited maintenance history.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 pkc |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/auth Version ^11.0|^12.0 | — | — |
illuminate/support Version ^11.0|^12.0 | — | — |
illuminate/database Version ^11.0|^12.0 | — | — |
Weekly Downloads
Info
- Last Published
- 8 months ago
- Created
- 8 months 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.