jambagecom/tslib-fetce
Only one release arrived in the last 12 months, while the repository has no commits or active maintainers in three months. One registry maintainer and no security policy add continuity risk, although the package is neither deprecated nor archived.
60%
Total Score
50
100
86
75
Health Score Breakdown
Only one account has registry publish access, leaving little visible publishing redundancy; recent release activity provides some compensation but not much.
The package has existed since January 2019 with 24 releases, but only one release in the last 12 months; this slowdown raises maintenance concerns despite a substantial history.
The repository recorded zero commits and zero active maintainers during the last three months, a concrete sign of currently quiet maintenance.
The linked repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled.
Version 0.11.0 is not a stable major release, which increases compatibility uncertainty for adopters even though it is not marked as a prerelease.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Franz Holzinger |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 typo3/cms-core Version ^13 || ^14 | — | — |
jambagecom/div2007 Version ^2.4.2 | — | — |
Weekly Downloads
Info
- Last Published
- 3 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.