omnipay/braintree
The beta label and absent security scanning add uncertainty. The repository remains licensed, tested, and unarchived, but the long release gap makes this a poor default dependency choice.
43%
Total Score
50
100
71
75
Health Score Breakdown
The latest registry release was published in November 2018, with no releases in the last 12 months. This nearly eight-year gap is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, indicating no current maintenance activity.
There were no new or closed issues or pull requests in the last month, while 16 issues and 10 pull requests remain open, suggesting limited current project attention.
Composer build tooling is present, but no security scanning tools were detected. The build setup is established, while security-maintenance visibility is limited.
The repository has no security policy, leaving no documented channel or process for reporting and handling security issues.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Barry vd. Heuvel |
| Kayla Daniels |
| Omnipay Contributors |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 omnipay/common Version ^3 | — | — |
braintree/braintree_php Version ^3.0 | — | — |
Weekly Downloads
Info
- Last Published
- 7 years ago
- Created
- 10 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.