Efficiently modify strings containing ANSI escape codes
78%
Total Score
63
100
100
70
50
No build attestation is present, so consumers cannot independently verify how the published artifact was produced. A trusted publisher identity of GitHub is useful context but does not replace provenance.
A prepare lifecycle script runs during installation, adding some supply-chain and install-time complexity. The repository's explicit build and test tooling provides context, but does not remove the extra execution surface.
The package is backed by a matching repository owned by an individual account, not an organization. The direct project match is positive, while individual ownership leaves less formal maintenance redundancy.
All two recent commits came from one contributor, giving the project a narrow short-term maintenance base. This is a real continuity risk because the repository owner is an individual rather than an organization.
The repository had two commits in the last three months, so activity is present but limited in volume.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ansi-styles Version ^6.2.1 | — | — |
is-fullwidth-code-point Version ^5.0.0 | — | — |
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.