The project has tests, release notes, a clear MIT license, and a substantial documented source tree. Its workflow uses three unpinned actions and the repository has no security policy, which adds maintenance and build-hygiene concerns.
68%
Total Score
50
100
75
The registry namespace and repository owner match, and the source is owned by the same individual account rather than an organization; this is consistent ownership but indicates a limited backing structure.
The repository recorded zero commits and zero active maintainers over the last 3 months. Recent releases and a recent push provide some compensation, but the short-term maintenance pause remains a concern.
There were no new or closed issues and no new or merged pull requests in the last month, indicating limited recent collaboration activity.
The repository has no published security policy, leaving vulnerability-reporting and response expectations unclear for a package handling purchase and subscription integrations.
The sole workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, all 3 action references are unpinned, which is a build-integrity hygiene concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
google/auth Version ^1.50 | — | — |
nesbot/carbon Version ^3.11 | — | — |
guzzlehttp/guzzle Version ^7.10 | — | — |
symfony/serializer Version ^8.0 | — | — |
symfony/property-access Version ^8.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.