tnw/soap-client
Its small dependency surface, tests, and MIT license make adoption straightforward. The repository has no recent commits, and it does not name this package, so future fixes and ownership are uncertain.
55%
Total Score
50
100
81
75
Health Score Breakdown
There were no commits and no active maintainers in the last three months. Combined with the last push in 2023, this indicates stalled maintenance and raises the risk that defects will remain unresolved.
Only one registry account has publish access, which limits publishing redundancy. The organization-owned repository provides some backing, so this is a modest concern rather than a severe ownership risk.
The package has nine releases since February 2018, but none in the last 12 months and its latest release was in June 2023, roughly three years ago. This is a meaningful maintenance concern.
The repository name does not match the package name and its README does not mention the package. Although a name mismatch can occur in a monorepo, the lack of any README mention makes package ownership less transparent.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap, not evidence that the package is unsafe.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 David de Boer |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 psr/log Version * | — | — |
symfony/event-dispatcher Version >=2.8 | — | — |
Weekly Downloads
Info
- Last Published
- 3 years ago
- Created
- 8 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.