The release has one registry maintainer and no repository security policy or scanning, limiting visible maintenance safeguards. MIT licensing, tests, and documentation provide useful adoption support, but do not offset the thin project backing.
42%
Total Score
25
71
75
The package has had no releases in the last 12 months, despite being about 712 days old, and its latest release was about two years ago. This is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating little current maintenance capacity.
Only one account has registry publishing access. Because the project backing is a user-owned repository rather than an organization, there is limited visible redundancy if that maintainer becomes unavailable.
The repository uses Composer but reports no security-scanning tools, so dependency and repository security maintenance is less visible than it could be.
The linked repository has no security policy, leaving no documented reporting process for consumers or maintainers. This is a transparency and maintenance gap, though not evidence of maliciousness.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
apimatic/core Version ~0.3.11 | — | — |
apimatic/unirest-php Version ^4.0.0 | — | — |
apimatic/core-interfaces Version ~0.1.5 | — | — |
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.