The MIT license, detailed documentation, and clean install setup support adoption. The project lacks a security policy or scanning, while its small audience and thin publishing base leave limited evidence of long-term support.
64%
Total Score
67
100
83
83
Only one registry account is listed with publish access, which limits visible publishing redundancy. The organization-owned repository provides some compensation for that thin registry maintainer list.
There are four releases clustered within roughly four days, followed by about five months without another release despite the package being about 163 days old. That gives limited evidence of an established maintenance cadence.
There were no commits and no active maintainers in the last three months. For a package this young, that is meaningful evidence that maintenance may have paused.
The repository has zero stars and forks and only one watcher, offering little supporting evidence of community adoption or review.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe risk by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
apimatic/core Version ~0.3.17 | — | — |
apimatic/unirest-php Version ^4.0.6 | — | — |
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.