ritechoice23/taggable
Usable with caveats: it is licensed, documented, tested in the repository, and not deprecated or archived. However, it has had no commits in three months, only two releases clustered on one day, and a very small public contributor footprint, so maintenance continuity is uncertain.
58%
Total Score
38
100
89
60
Health Score Breakdown
The repository recorded zero commits and zero active maintainers during the last three months. For a library dependency, this is a meaningful warning about stalled maintenance.
One of five workflows uses pull_request_target, which can carry elevated workflow risk, but no untrusted checkout or script-injection patterns were detected.
A post-autoload-dump install-time script is present. This is not inherently unsafe, but it adds installation behavior that should be reviewed before adoption.
Only one registry publishing account is listed. That is a limited operational base and creates continuity risk if the maintainer becomes unavailable.
The registry namespace and repository owner match, but the owner is an individual account rather than an organization, so there is limited evidence of institutional backing.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Daramola Babatunde Ebenezer |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 illuminate/contracts Version ^11.0||^12.0 | — | — |
spatie/laravel-package-tools Version ^1.16 | — | — |
Weekly Downloads
Info
- Last Published
- 10 months ago
- Created
- 10 months 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.