Its BSD-3-Clause license file conflicts with the proprietary manifest, and all four workflow actions are unpinned. Tests, a release note, and repository tooling provide useful supporting evidence.
55%
Total Score
50
80
50
A BSD-3-Clause license file is present in both the artifact and repository, so the release is licensed; however, the manifest declares proprietary licensing, creating a meaningful metadata mismatch.
The package has only two releases, both on March 19, 2023, with no releases in the last 12 months. This indicates a largely inactive release history, though a template can remain stable once established.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long period without releases. The project is not archived, but current maintenance capacity is not demonstrated.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, or audit findings. However, all four referenced actions are unpinned, leaving avoidable build-integrity hygiene risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
phayne-io/php-exception Version ^1.0@dev | — | — |
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.