Usable with caveats: it has a long release history, a maintained organization-backed repository, tests, documentation, and a license. The main concern is no commits or issue activity in the last three months, alongside limited repository security tooling and unspecified workflow token permissions.
68%
Total Score
67
100
89
88
The repository recorded zero commits and zero active maintainers in the last three months, which is the strongest maintenance concern even though the latest release and repository push provide some compensating evidence.
There are three open issues and four open pull requests, but no issues or pull requests were opened or closed in the last three months, suggesting limited recent project interaction.
The repository has only 2 stars and 8 forks, indicating a small user base; this is weak supporting evidence and does not outweigh the package's release history and organization backing.
Composer build tooling is present, but no security scanning tool was detected; this is a transparency gap rather than evidence that the package is unsafe.
The release workflow does not declare top-level token permissions, so its default permissions are less explicit than preferred, although it declares no top-level write access.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
johnbillion/extended-cpts Version ^5.0 | — | — |
yahnis-elsts/plugin-update-checker Version ^5.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.