wp-pay-extensions/contact-form-7
Documentation and release notes are present, and the organization-backed project has a clear package structure. Recent work is sparse and concentrated in one contributor, while all four workflow actions are unpinned; pin a reviewed version if adopting.
68%
Total Score
67
100
93
67
Health Score Breakdown
The package runs post-install and post-update Composer scripts. These increase install-time execution exposure and warrant some caution, although the signal does not establish that the scripts are unsafe.
One contributor made 100% of the commits in the last 3 months. Organization backing provides some handoff capacity, but no second recently active contributor is shown.
Only 1 commit was recorded in the last 3 months, with 1 active maintainer. This is sparse recent activity for a maintained integration and lowers confidence in response capacity.
Composer build tooling is present, but no security-scanning tooling was detected. The missing scanning layer is a maintenance and assurance gap, not evidence of a vulnerable release.
The repository has no security policy. For a payment-processing integration, this reduces transparency about how security issues should be reported and handled.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Pronamic |
| Remco Tolsma |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 wp-pay/core Version ^4.25 | — | — |
automattic/jetpack-autoloader Version ^3.0 || ^4.0 || ^5.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 month ago
- Created
- 6 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.