rlankhorst/wp-consent-level-api
Healthy and suitable to depend on. It has recent stable releases, active work from three contributors, clear licensing, tests, and a correctly linked WordPress repository; the main gaps are the missing security policy and undeclared workflow token permissions.
86%
Total Score
100
100
94
67
Health Score Breakdown
Composer build tooling is present, supporting reproducible project workflows. No security scanning tools were detected, leaving a modest transparency gap.
The repository has no security policy, so the process for reporting and handling vulnerabilities is not documented. This is a transparency gap, but it is not evidence that the package is unsafe to use.
The sole workflow lacks top-level token permissions and does not explicitly declare read-only access. No top-level write permissions or other dangerous workflow behavior were observed, so this is a limited workflow-hygiene concern.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 7 days ago
- Created
- 3 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.