The package includes clear consumer documentation, tests, and a stable Composer dependency setup. Workflow pinning and the lack of a security policy leave modest transparency and build-hygiene gaps.
84%
Total Score
100
100
93
67
Composer is used for builds, but no security-scanning tool was detected. This is a modest engineering-hygiene gap rather than evidence of unsafe or unmaintained code.
The repository has no published security policy, making vulnerability reporting and response expectations less transparent for consumers.
The single workflow was fully analyzed with no untrusted checkout, script injection, or audit findings, and it has no top-level write permissions. However, all 3 action references are unpinned, leaving a build-reproducibility and action-supply-chain hygiene gap.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
mf2/mf2 Version ^0.4||^0.5 | — | — |
p3k/http Version ^0.2.1 | — | — |
p3k/picofeed Version 0.1.41 | — | — |
cebe/markdown Version ^1.1.0 | — | — |
masterminds/html5 Version ^2.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.