The narrow dependency set and stable release reduce complexity. However, the package has had no registry release since February 2020, no recent commits, and its README describes Guzzle rather than this WordPress package.
45%
Total Score
75
100
75
75
The latest release was on February 6, 2020, with no releases in the last 12 months. That long silence is a substantial abandonment concern despite the package having seven releases overall.
The artifact includes a README and changelog, but the README excerpt identifies and documents Guzzle rather than bonnier/wp-bonnier-purchase. This weakens transparency for consumers even though the package includes basic documentation files.
The repository recorded zero commits and zero active maintainers in the last three months. The repository is not archived, but there is no recent activity to demonstrate ongoing maintenance.
Composer is used as a build tool, which is positive, but no security-scanning tools were detected. For a package containing application code and bundled dependencies, that is a maintenance and hygiene gap.
The linked repository has no security policy. This does not prove a security problem, but it provides little guidance for reporting or handling vulnerabilities.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.3 | — | — |
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.