A single registry maintainer and no security policy limit resilience and disclosure transparency. The MIT declaration, release notes, README, and non-archived repository provide useful supporting evidence.
68%
Total Score
50
93
75
Only one account has registry publish access, which leaves little publishing redundancy. The linked repository is user-owned rather than organization-owned, so there is no provided backing signal to compensate for that narrow base.
The package has existed since December 2021 and released v1.1.2 recently, but only one release appeared in the last 12 months. That suggests limited ongoing release activity despite the recent update.
The repository recorded zero commits and zero active maintainers in the last three months. A release was still pushed recently, but the lack of recent commit activity weakens evidence of sustained maintenance.
The repository has no security policy, so users have no documented channel or process for reporting security issues. This is a transparency gap, though not evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/yaml Version >=5.2 | — | — |
symfony/orm-pack Version >=2.2 | — | — |
rbdwllr/reallysimplejwt Version ^4.0 | — | — |
symfony/framework-bundle Version >=5.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.