gipfl/protocol
The MIT licensing and matching repository make the package transparent to adopt. Its small project footprint, absent tests and security scanning, and no releases in the last 12 months leave maintenance risk.
62%
Total Score
63
100
72
88
Health Score Breakdown
One registry maintainer is consistent with a small organization-backed project; the organization ownership provides some backing, but the observed maintenance activity remains limited.
A README is present, but the package and repository report no tests or changelog. Missing tests are a meaningful gap for a library, while the absent changelog is less important because this release has no GitHub release notes.
The package has existed since February 2019 and has four releases, but none were published in the last 12 months and the median interval is about 581 days, indicating slow maintenance.
There were no commits and no active maintainers in the last three months, reinforcing the release-history evidence of currently low maintenance activity.
There are no open issues or pull requests and no activity in the last month. This is not inherently unhealthy for a small stable library, but it offers little evidence of active community maintenance.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Thomas Gelf |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 react/stream Version ^1 | — | — |
evenement/evenement Version ^2|^3 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year 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.