tbachert/spi
The small repository matches the package, includes tests, and has a clear Apache-2.0 license. No recent commits and no security policy reduce confidence in ongoing maintenance and security response.
64%
Total Score
50
100
88
83
Health Score Breakdown
The package is linked to a user-owned repository rather than an organization, so the small registry namespace does not have organizational backing to compensate for its thin recent activity.
The package has had 9 releases since March 2024, but none in the last 12 months; the latest release was over a year ago. This is a meaningful maintenance warning despite its previously regular release intervals.
There were no commits or active maintainers in the three months measured. Combined with no releases in the last 12 months, this supports a caution about slowing maintenance.
The repository uses Composer build tooling, but no security-scanning tool was detected. The missing scanner is a modest transparency and hygiene gap, not evidence that the package is unsafe.
The repository has no published security policy, leaving vulnerability-reporting and response expectations unclear. This is a maintenance and transparency gap for a package that executes as a Composer plugin.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 composer/semver Version ^1.0 || ^2.0 || ^3.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year ago
- Created
- 2 years 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.