fw4/whise-api
Clear tests, release notes, and an organization-backed repository make integration easier. The missing security policy and unpinned workflow actions leave transparency and build-reproducibility gaps.
66%
Total Score
67
88
75
Health Score Breakdown
The package has 30 releases over roughly six years, but only one release in the last 12 months despite a historical median interval of about 45 days. This suggests maintenance has slowed, though the latest release is recent enough to avoid an abandonment verdict.
There were zero commits and zero active maintainers in the last three months. Combined with the low recent release count, this is a meaningful maintenance and abandonment concern.
No issues or pull requests were opened or closed in the last month, with one issue and one pull request currently open. This indicates limited recent project activity, although the small backlog is not severe by itself.
Composer build tooling is present, but no security scanning tools were detected. That leaves a modest assurance gap for a dependency library.
The repository has no security policy. For a library handling API authentication and credentials, this reduces transparency around vulnerability reporting and response.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ~6.0|~7.0 | — | — |
ocramius/package-versions Version ^2.1 | — | — |
Weekly Downloads
Info
- Last Published
- 10 months ago
- Created
- 6 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.