omnipay/pin
The MIT license, tests, release notes, and limited runtime dependencies support predictable integration. The repository is not archived and the package is not deprecated, but ongoing maintenance evidence is limited.
45%
Total Score
50
100
81
88
Health Score Breakdown
The package has five releases but no release in the last 12 months, and its latest registry release was March 25, 2016. This is strong evidence of staleness for a dependency.
There were no commits and no active maintainers in the three months measured, indicating that current maintenance capacity is absent.
There was no recent issue or pull-request activity and one issue remains open, providing little evidence of active support.
Composer build tooling is present, but no security-scanning tooling was detected. This is a modest transparency and maintenance gap rather than a standalone severe risk.
The repository has no security policy, leaving vulnerability-reporting expectations undocumented. This matters for a payment-processing integration, though it is secondary to the stale maintenance evidence.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Adrian Macneil |
| Omnipay Contributors |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 omnipay/common Version ~2.0 | — | — |
Weekly Downloads
Info
- Last Published
- 10 years ago
- Created
- 12 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.