natilosir/bot
The README is substantial, the dependency set is focused, and installation has no lifecycle scripts. The project is only 14 days old, with all five recent commits from one contributor and no security scanning or policy. Follow its maintenance closely before making it a core dependency.
61%
Total Score
67
100
93
83
Health Score Breakdown
Only one registry account has publish access. Because project backing identifies an individual owner rather than an organization, this leaves limited publishing redundancy.
One contributor made all five commits in the last three months, giving the project a complete single-contributor concentration. With individual rather than organizational backing, loss of that maintainer would materially affect continuity.
Composer build tooling is present, but no security-scanning tools were detected. That is a modest transparency and maintenance gap for a package handling bot integrations.
The repository has no security policy. This reduces transparency about how vulnerabilities should be reported and handled, although it is not by itself evidence of unsafe code.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Natilos.ir |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/http Version * | — | — |
illuminate/database Version * | — | — |
illuminate/container Version * | — | — |
Weekly Downloads
Info
- Last Published
- 4 days ago
- Created
- 18 days 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.