drago-ex/project-permission
Clear documentation, MIT licensing, active releases, and organization backing reduce adoption risk. Pin workflow actions and verify maintenance continuity before relying on it for critical access control.
72%
Total Score
67
50
100
63
Health Score Breakdown
Fifteen runtime dependencies, including several related project modules, create a relatively broad dependency surface and increase upgrade coordination for consumers.
post-install-cmd and post-update-cmd scripts run during installation or updates, adding operational and review overhead for consumers.
One contributor made all six recent commits, leaving maintenance highly concentrated. Organization backing helps provide continuity potential but does not itself demonstrate a second active maintainer.
Six commits were made in the last three months, indicating recent activity, but all came from one active maintainer.
No repository security policy is present, leaving vulnerability reporting and response expectations undocumented.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 nette/di Version ^3.1 | — | — |
drago-ex/form Version ^2.0 | — | — |
drago-ex/utils Version ^2.0 | — | — |
nette/security Version ^3.1 | — | — |
drago-ex/database Version ^3.0 | — | — |
Weekly Downloads
Info
- Last Published
- 3 months ago
- Created
- 4 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.