marekmiklusek/telegram-logger
It has recent releases, active commits, a stable version, and repository tests. The project is small and lacks a security policy, while both workflow actions are unpinned.
72%
Total Score
63
100
94
83
Health Score Breakdown
Only one registry account has publishing access. This is a resilience concern, though repository activity shows that the maintainer is currently active.
The repository is owned by an individual account rather than an organization, so the single-maintainer and bus-factor concerns are not offset by visible organizational backing.
One contributor made all 12 commits in the last 3 months, leaving maintenance highly concentrated and increasing continuity risk.
Composer build tooling is present, but no security scanning tools were detected, leaving security-oriented maintenance less visible.
The repository has no security policy, so the process for reporting and handling vulnerabilities is not documented.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Marek Miklusek |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/support Version ^13.0 | — | — |
illuminate/contracts Version ^13.0 | — | — |
Weekly Downloads
Info
- Last Published
- 22 days ago
- Created
- 1 year 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.