@builderbot/bot
core typescript
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
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): Scoped package @builderbot/bot; Levenshtein match to 'got' is a false positive for scoped names. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): Scoped package; no impersonation intent, established package with 211 versions. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package; no impersonation intent, established package with 211 versions. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped package; no impersonation intent, established package with 211 versions. | ai | |
| phantom-deps | phantom-dep:cors | AI (phantom-deps): Bundled dist package; deps declared in package.json and consumed via rollup build. | ai | |
| phantom-deps | phantom-dep:mime-types | AI (phantom-deps): Bundled dist package; deps declared in package.json and consumed via rollup build. | ai | |
| phantom-deps | phantom-dep:picocolors | AI (phantom-deps): Bundled dist package; deps declared in package.json and consumed via rollup build. | ai | |
| phantom-deps | phantom-dep:body-parser | AI (phantom-deps): Bundled dist package; deps declared in package.json and consumed via rollup build. | ai | |
| phantom-deps | phantom-dep:follow-redirects | AI (phantom-deps): Bundled dist package; deps declared in package.json and consumed via rollup build. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.4.1 | 8 / 20 | |
| 1.4.0 | 8 / 20 | |
| 1.3.15 | 8 / 20 | |
| 1.3.14 | 8 / 20 | |
| 1.3.13 | 8 / 20 | |
| 1.3.12 | 8 / 20 | |
| 1.3.11 | 8 / 20 | |
| 1.3.10 | 8 / 20 | |
| 1.3.8 | 8 / 20 | |
| 1.3.7 | 8 / 20 | |
| 1.3.5 | 8 / 20 | |
| 1.3.4 | 8 / 20 | |
| 1.3.3 | 8 / 20 | |
| 1.3.1 | 8 / 20 | |
| 1.2.9 | 8 / 20 | |
| 1.2.8 | 8 / 20 | |
| 1.2.7 | 8 / 20 | |
| 1.2.6 | 8 / 20 |
v1.4.1
2 findingsPackage name '@builderbot/bot' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
2 findingsPackage name '@builderbot/bot' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.15
2 findingsPackage name '@builderbot/bot' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.14
2 findingsPackage name '@builderbot/bot' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.13
2 findingsPackage name '@builderbot/bot' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.12
2 findingsPackage name '@builderbot/bot' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.11
2 findingsPackage name '@builderbot/bot' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.10
2 findingsPackage name '@builderbot/bot' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.8
2 findingsPackage name '@builderbot/bot' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.7
2 findingsPackage name '@builderbot/bot' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
2 findingsPackage name '@builderbot/bot' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
2 findingsPackage name '@builderbot/bot' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
2 findingsPackage name '@builderbot/bot' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
2 findingsPackage name '@builderbot/bot' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.9
2 findingsPackage name '@builderbot/bot' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
2 findingsPackage name '@builderbot/bot' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
2 findingsPackage name '@builderbot/bot' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
2 findingsPackage name '@builderbot/bot' is 1 edit(s) away from popular package 'got'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.