Clear documentation, tests, release notes, and regular releases support dependable maintenance. The single active contributor and missing security policy leave some continuity and security-process risk despite organizational ownership and safe workflow patterns.
82%
Total Score
75
100
94
67
All 10 recent commits came from one contributor, creating a meaningful continuity risk; organization ownership provides some ability to hand off maintenance but does not show a second active contributor.
The repository received 10 commits in the last 3 months, showing recent work, but all were produced by one active maintainer.
Composer and task build tooling are present, but no security-scanning tooling was detected, leaving a modest automated security-process gap.
The repository has no published security policy, reducing transparency about how vulnerabilities should be reported and handled.
None of the 11 workflows declares top-level token permissions, although no workflow has top-level write permissions and two constrain permissions at job level; this is a configuration hygiene concern rather than a severe workflow risk.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
alma/alma-php-client Version ^2.6 | — | — |
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.