mjelamanov/psr18-guzzle
The small maintainer base and lack of recent repository commits leave limited evidence of ongoing maintenance. Tests, release notes, a matching repository, and read-only workflow permissions provide useful transparency, but all three workflow actions are unpinned and no security policy is present.
68%
Total Score
50
100
94
67
Health Score Breakdown
The package and repository are owned by the same individual account, so the single registry maintainer reflects the project's actual backing rather than an organization publishing arrangement; this still leaves a thin maintainer base.
No commits or active maintainers were recorded in the last three months, which weakens evidence of ongoing maintenance despite the recent release.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest repository hygiene gap.
The repository has no security policy, making vulnerability reporting and response expectations less transparent.
The single workflow was fully analyzed, uses read-only permissions, and has no reported findings, but all three action references are unpinned, so their fetched revisions are not fixed.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Mirlan Jelamanov |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 psr/http-client Version ^1.0 | — | — |
guzzlehttp/guzzle Version ^6.0 | — | — |
Weekly Downloads
Info
- Last Published
- 10 months ago
- Created
- 7 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.