sweetchuck/robo-stringy
The repository is not archived, matches the package, and includes tests. Documentation is skeletal, with TODOs for installation and usage, while install-time scripts and missing security tooling add maintenance risk.
45%
Total Score
0
100
69
50
Health Score Breakdown
The latest release was in January 2020, with no releases in the last 12 months and only two releases overall. That long release gap materially raises abandonment and compatibility risk.
The repository recorded zero commits and zero active maintainers in the last three months. Although it is not archived, there is no recent development evidence to offset the stale release history.
The package runs post-install and post-update scripts, increasing installation complexity and the amount of code executed during dependency operations. No provided signal shows these scripts are unnecessary or independently verified.
Tests are present and the package includes a README, which are positive signs, but the README leaves installation and usage as TODOs and provides little practical guidance to consumers.
The project uses Composer and Robo, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Dávid Andor |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 consolidation/robo Version ^2.0 | — | — |
danielstjules/stringy Version ^3.1 | — | — |
Weekly Downloads
Info
- Last Published
- 6 years ago
- Created
- 8 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.