@snort/bot
Simple bot framework
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:got | AI (typosquat): @snort/bot is a scoped package in the Nostr ecosystem, not a typosquat of 'got'. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): Scoped @snort namespace; no relation to 'koa'. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @snort namespace; no relation to 'joi'. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped @snort namespace; no relation to 'zod'. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.2.2 | 1 / 2 | |
| 1.2.1 | 2 / 2 | |
| 1.2.0 | 2 / 2 | |
| 1.1.1 | 2 / 2 | |
| 1.1.0 | 2 / 2 | |
| 1.0.17 | 2 / 2 |
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.