@ch1c0t/io
A global.IO in vein of Ruby's IO module.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:koa | AI (typosquat): Scoped package @ch1c0t/io; not impersonating koa. Name similarity is coincidental. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped package @ch1c0t/io; not impersonating got. Name similarity is coincidental. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @ch1c0t/io; not impersonating pg. Name similarity is coincidental. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @ch1c0t/io; not impersonating qs. Name similarity is coincidental. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @ch1c0t/io; not impersonating joi. Name similarity is coincidental. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped package @ch1c0t/io; not impersonating zod. Name similarity is coincidental. | ai | |
| typosquat | typosquat.levenshtein:pino | AI (typosquat): Scoped package @ch1c0t/io; not impersonating pino. Name similarity is coincidental. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.1.0 | 0 / 2 | |
| 0.0.7 | 0 / 1 | |
| 0.0.6 | 0 / 1 | |
| 0.0.5 | 0 / 1 | |
| 0.0.4 | 0 / 1 | |
| 0.0.3 | 0 / 1 | |
| 0.0.2 | 0 / 1 | |
| 0.0.1 | 0 / 1 |
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.