gipfl/process
Its small, focused file set and organization-owned repository keep the maintenance burden understandable. The missing README, absent security policy, and lack of security scanning reduce transparency for consumers, despite a declared MIT license and no install-time scripts.
61%
Total Score
75
75
75
Health Score Breakdown
The package has had five releases since October 2021, but none in the last two years; this suggests a slowing maintenance cycle for a dependency that may still need fixes.
There were no commits or active maintainers in the last three months, consistent with the long release gap and raising abandonment risk.
The project uses Composer, but no security scanning tools were detected; that is a modest transparency and maintenance gap.
The linked repository has no security policy, leaving no documented path for reporting vulnerabilities or handling security fixes.
Version v0.5.0 is not a stable major release, so its API may still change, although it is not marked as a prerelease.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Thomas Gelf |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 gipfl/json Version >=0.1 | — | — |
react/promise Version >=2 | — | — |
gipfl/linux-health Version >=0.2 | — | — |
react/child-process Version >=0.6 | — | — |
Weekly Downloads
Info
- Last Published
- 2 years ago
- Created
- 4 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.