Create JWT tokens
68%
Total Score
caution
Recent releases are present, but all recent repository work comes from one contributor and no security policy is published.
One contributor made all two commits in the last three months. Organization ownership provides some handoff capacity, but no second active contributor is shown to reduce the immediate concentration risk.
Only two commits were recorded in the last three months. That shows some recent activity, but the volume is low and provides limited evidence of maintenance capacity.
Composer is used for builds, but no security scanning tool is present. For a small Craft CMS plugin this is a hygiene limitation rather than a severe supply-chain concern.
The repository has no security policy. That reduces transparency for reporting and handling vulnerabilities, with no provided compensating process.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
craftcms/cms Version ^5.0.0 | — | — |
firebase/php-jwt Version ^7.0.0 | — | — |
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.