@bgord/bun
Clone the repository
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 |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Used to decode image placeholder data-URI bytes; legitimate image processing pattern stable for this package. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): bunx only-allow bun is a standard package-manager enforcement pattern; stable and benign for this package. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): @bgord/bun is a scoped Bun-runtime utility package, not a typosquat of yup; name similarity is coincidental. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.19.4 | 4 / 23 | |
| 1.19.3 | 4 / 23 | |
| 1.18.14 | 4 / 24 | |
| 1.18.13 | 4 / 24 | |
| 1.18.12 | 4 / 24 | |
| 1.18.11 | 4 / 24 | |
| 1.17.1 | 4 / 23 | |
| 1.17.0 | 4 / 23 | |
| 1.16.4 | 4 / 23 |
v1.19.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.