getcandy/stripe
The package has a clear README and tests, and its organization backing is a modest positive. Unpinned workflow actions and no security policy add hygiene concerns for a payment integration.
39%
Total Score
50
75
50
Health Score Breakdown
Only three releases were published, with no release in over four years; the long gap is strong evidence of abandonment risk despite the package not being deprecated.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity for over four years.
The linked repository has no security policy. For a payment integration, this is a meaningful transparency and maintenance gap.
The assessed version is 1.0-alpha3, and all recent releases are prereleases. The README also identifies the addon as alpha, limiting confidence for production use.
All three analyzed action references are unpinned, which weakens build reproducibility. The audit found no dangerous triggers, untrusted checkouts, script injection, or other reported findings, partly offsetting the concern.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 GetCandy |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 getcandy/core Version ^2.0-beta12 | — | — |
livewire/livewire Version ^2.0 | — | — |
stripe/stripe-php Version ^7.114 | — | — |
Weekly Downloads
Info
- Last Published
- 4 years ago
- Created
- 4 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.