The package is a very small six-file project with no tests, security scanning, or security policy. Its repository is not archived and the package has a clear MIT license and README, but there have been no commits or releases for about four years.
43%
Total Score
0
100
75
67
The latest release was about four years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a package intended to remain a maintained application integration.
The repository recorded no commits and no active maintainers in the last three months, reinforcing the long release gap rather than showing ongoing maintenance between releases.
The package contains only six files, including one source class and one service provider, with no tests or broader project structure visible. The small footprint may fit a focused integration, but it offers little evidence of maturity.
Composer is used for the build, which is appropriate, but no security scanning tools are configured. This is a maintenance and verification gap, though not severe by itself.
The repository has no security policy, reducing transparency about vulnerability reporting and maintenance expectations. The absence matters more alongside the stale activity.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
faultline/faultline Version * | — | — |
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.