pschilly/dcs-server-bot-api
The license, README, changelog, matching repository, and Composer tooling make the package transparent. One maintainer and workflow weaknesses add some risk, while the long release and commit pause is the main concern.
55%
Total Score
50
100
86
67
Health Score Breakdown
Only one registry account has publish access. That is a limited publishing base for a user-owned project and leaves less visible redundancy if the maintainer becomes inactive.
The registry and repository are owned by the same individual account, which supports clear ownership but provides no organization-level backing to compensate for the thin maintainer base.
The package released 13 times during its initial period, but its latest release was over a year ago and there were no releases in the last 12 months, indicating a substantial maintenance pause.
There were no commits and no active maintainers in the last three months. Combined with the absence of releases in the last 12 months, this supports a meaningful maintenance concern.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Schilly |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/contracts Version ^10.0||^11.0||^12.0 | — | — |
spatie/laravel-package-tools Version ^1.16 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year 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.