aiarmada/cashier-chip
Clear documentation, an MIT declaration, and organization ownership make adoption easier. The repository lacks a security policy and automated security scanning, while the pre-1.0 version leaves compatibility risk.
72%
Total Score
100
100
79
67
Health Score Breakdown
The package published 35 releases in its first 17 days, but the latest registry release was 104 days ago. A repository push 4 days before collection provides some compensating evidence, but release maintenance is still uncertain.
Composer is used as the build tool, but no security-scanning tools were detected. That is a modest transparency and maintenance gap rather than evidence the package is unsafe.
The linked repository has no security policy, leaving reporting and response expectations undocumented for a package handling payment integrations.
Version v0.1.34 is not on a stable major version, so compatibility may change before 1.0. It is not marked prerelease and recent prerelease share is 0%, which limits the concern.
No GitHub Actions workflows were present, so the audit found no risky workflow behavior. This also means there is no visible workflow-based automation or security checking to support the project.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 aiarmada/chip Version self.version | — | — |
aiarmada/commerce-support Version self.version | — | — |
spatie/laravel-webhook-client Version ^3.6.2 | — | — |
Weekly Downloads
Info
- Last Published
- 4 months ago
- Created
- 4 months 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.