MIT licensing, a working test suite, and a matching organization-owned repository provide useful transparency. The project has no security scanning or published security policy, so maintenance and security oversight appear limited.
58%
Total Score
75
83
50
The package has 25 releases since September 2017, but its latest release was over three years ago and it had no releases in the last 12 months. That strongly lowers confidence in ongoing maintenance, though it is not deprecated.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release gap. The repository is not archived, so this indicates stagnation rather than confirmed abandonment.
Composer build tooling is present, but no security scanning tools were detected. This is a meaningful oversight gap for a maintained SDK, although it is not evidence of a security incident.
The linked repository has no security policy. That reduces transparency about vulnerability reporting and response, especially alongside the lack of recent activity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
respect/validation Version ^1.1 | — | — |
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.