Aegis v1.16.0 appears healthy and reasonably mature for adoption: it has a stable release, 27 releases over about 358 days with 26 in the last 12 months, recent repository activity, substantial tests and documentation, a matching source repository, and no deprecation or install-time lifecycle scripts. The main concerns are that all 29 commits in the last 3 months came from one contributor, the repository has minimal observed popularity, and no security policy or security-scanning tooling is present; these are meaningful transparency and resilience gaps but are partly offset by organization ownership, ongoing releases, and strong package scaffolding.
82%
Total Score
90
100
89
90
One contributor made all 29 commits in the last 3 months, creating a real continuity and bus-factor concern. Organization ownership provides some potential handoff capacity, but no second active contributor is evidenced.
The repository has only 1 star, 0 forks, and 0 watchers, providing little external adoption evidence; this is a supporting caution rather than a decisive health issue.
Composer build tooling is present, but no security-scanning tools are detected; for an RBAC package, the missing security automation is a meaningful hygiene gap.
The repository has no security policy, leaving vulnerability-reporting expectations and disclosure procedures undocumented.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.