The package is documented, tested, licensed, and clearly tied to an organization-owned monorepo. Its small release history, prerelease status, and absent recent commit activity make long-term maintenance uncertain, while the repository has no security policy or scanning tools.
62%
Total Score
75
75
75
Only one release exists, published about 16 months ago, with no releases in the last 12 months. This limits evidence of an established release process and ongoing maintenance.
The repository recorded zero commits and zero active maintainers in the last three months. Although the repository is not archived, this provides weak evidence of current maintenance.
Composer is used as a build tool, which fits the package ecosystem, but no security scanning tools are reported. This is a modest transparency and maintenance gap rather than a severe risk.
The repository has no security policy. For a small library this is a transparency gap, though it does not by itself indicate that the release is unsafe to depend on.
The assessed version is 1.0.0-RC2 and all recent releases are prereleases. That indicates the API may not yet be considered stable, despite the major version number.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
apie/core Version self.version | — | — |
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.