The package has tests and an MIT license, but it lacks security scanning and a security policy. Its tiny README and no repository mention beyond the matching repository name also limit transparency for consumers.
42%
Total Score
0
71
75
The latest release was published in July 2021, and there have been no releases in roughly five years. That is strong evidence of abandonment risk despite the package having 12 releases overall.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release gap and indicating no visible ongoing maintenance.
The repository name matches the package, but the README does not mention the package name. That weakens ownership and documentation transparency slightly, although the name match is reassuring.
Composer build tooling is present, but no security-scanning tools were detected. That reduces assurance for a package with no recent maintenance activity.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a maintenance and transparency gap, though not proof of unsafe code.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
onesite/core Version ^1.0 | — | — |
guzzlehttp/guzzle Version ^6.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.