MIT licensing, a substantial README, repository tests, and read-only workflow permissions improve transparency. Organization backing helps, but the package is too new to establish dependable maintenance.
62%
Total Score
83
90
50
The package is zero days old with only two releases, so there is not yet enough release history to demonstrate sustained maintenance. The second release includes documented licensing changes, which provides limited transparency.
The repository recorded zero commits and zero active maintainers in the last three months, although the project is newly published. This leaves maintenance continuity unproven rather than showing established abandonment.
The linked repository has no security policy, leaving vulnerability reporting and response expectations unspecified. This is a transparency gap for a package intended for application use.
The single workflow was fully analyzed, uses read-only permissions, and has no detected injection or high-severity findings. All four action references are unpinned, which weakens build reproducibility and supply-chain hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.8.2 || ^8.0 | — | — |
laravel/framework Version ^12.0 || ^13.0 | — | — |
tijsverkoyen/css-to-inline-styles Version ^2.2.5 | — | — |
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.