The package is licensed and has repository tests, a changelog, and release notes. Its source repository does not identify the package, while recent commit activity is absent and CI references are entirely unpinned.
50%
Total Score
50
75
50
The package is 475 days old with eight releases, but only two releases in the last 12 months. This shows some release continuity while suggesting a slowing cadence.
The repository recorded zero commits and zero active maintainers in the last three months. That is a meaningful maintenance warning for a package that is still relatively young.
The linked repository name does not match the package name and its README does not mention the package. That leaves uncertainty about whether the repository is the actual source for this package.
The repository has no security policy. This is a modest transparency gap for a package handling application performance data, though it does not by itself indicate abandonment.
All 12 analyzed action references are unpinned, and the audit found a high-confidence bot-condition issue in the Dependabot auto-merge workflow. The pull-request trigger has no untrusted checkout or script-injection sink, so this is workflow hygiene risk rather than a severe release risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
rector/rector Version ^2.0 | — | — |
atendwa/filakit Version ^1.0 | — | — |
atendwa/support Version ^1.0 | — | — |
illuminate/contracts Version ^10.0||^11.0||^12.0 | — | — |
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.