wp-pay-extensions/restrict-content-pro
Seven releases in the last year and a current, stable version show dependable upkeep. The repository has tests and an organization behind it, but its security process and workflow pinning are basic.
72%
Total Score
83
94
50
Health Score Breakdown
Only one contributor was active in the last 3 months and that contributor made 100% of the recorded commits, leaving limited recent contributor redundancy; organizational backing partly offsets this.
Composer build tooling is present, but no security scanning tools were detected, leaving a maintenance and security-process gap.
The repository has no security policy, reducing transparency about vulnerability reporting and response expectations.
The sole workflow was fully analyzed with no audit findings or untrusted execution sinks, but all 3 action references are unpinned, weakening build reproducibility and action supply-chain hygiene.
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.28 | — | — |
pronamic/wp-money Version ^2.4 | — | — |
pronamic/wp-number Version ^1.4 | — | — |
wp-pay-gateways/mollie Version ^4.15 | — | — |
woocommerce/action-scheduler Version ^3.9 || ^4.0 | — | — |
Weekly Downloads
Info
- Last Published
- 2 months ago
- Created
- 8 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.