Clear documentation and licensing reduce adoption friction. The young 0.x release line still carries API-change risk, while repository activity and organizational backing support continued maintenance.
84%
Total Score
100
100
81
100
Five releases in about 7 weeks, with a median interval of about 2 days, show active early development. The short 52-day history means long-term maintenance is not yet established.
Composer build tooling is present, but no security-scanning tools were detected. That is a modest transparency and assurance gap rather than evidence of abandonment.
The release is not marked prerelease, but v0.3.2 is still before a stable major version, so consumers should expect greater API-change risk than with a mature 1.x package.
Both workflows were analyzed successfully, all two action references are pinned, and no dangerous audit findings were reported. One autorelease workflow has top-level write permissions, which is a mild least-privilege concern.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
automattic/jetpack-status Version ^6.2.0 | — | — |
automattic/jetpack-connection Version ^8.8.2 | — | — |
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.