REST API authentication for Nette Framework. Token auth, rate limiting, refresh tokens, CORS and scopes - zero boilerplate.
65%
Total Score
50
86
67
One registry maintainer is consistent with an individual-owned project, but it provides limited publishing redundancy as the package matures.
The package is only about four months old and has two releases, with the latest published about four months ago. That is limited evidence of sustained maintenance, though the short history also limits how much abandonment can be inferred.
The project uses Composer, but no security-scanning tooling was detected. For an authentication library, that leaves a modest assurance gap.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented for an authentication package.
The sole workflow was fully analyzed with no dangerous triggers or audit findings, but both of its two action references are unpinned. This is a workflow hygiene weakness rather than a severe risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
nette/di Version ^3.0|^3.1|^3.2 | — | — |
nette/schema Version ^1.1 | — | — |
nette/caching Version ^3.0|^3.1|^3.2 | — | — |
nette/database Version ^3.0|^3.1|^3.2 | — | — |
nette/application Version ^3.0|^3.1|^3.2 | — | — |
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.