response-interop/interface
Healthy and reasonable to use, with minor maintenance and security-process caveats. It has a clear MIT license, strong documentation, a stable release with notes, matching repository ownership, and no deprecation or workflow-risk findings. Recent activity is sparse and the repository lacks a security policy and explicit workflow token permissions.
78%
Total Score
75
100
89
67
Health Score Breakdown
Only one account has registry publishing access, which is a narrow publishing base. The organization-backed repository provides some compensation, so this is not treated as a severe risk.
Only two commits from one active maintainer were recorded in the last three months, which is sparse activity, though it aligns with a small, recently released interface package.
The repository has only 2 stars and 3 forks, indicating limited adoption evidence. Popularity is supporting evidence rather than a health verdict, and the package has stronger direct documentation and release signals.
Composer build tooling is present, but no security scanning tools were detected. This is a process gap, not evidence of unsafe code by itself.
No repository security policy was found, reducing transparency about vulnerability reporting and response procedures.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Paul M. Jones |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 2 months ago
- Created
- 9 months ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.