@buoy-gg/core
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is a sibling @buoy-gg scoped package in the same monorepo; not a third-party injection. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @buoy-gg package; 'core' suffix is a legitimate sub-package name, not a typosquat of 'cors'. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.1.14 | 4 / 3 | |
| 2.1.13 | 4 / 3 | |
| 2.1.12 | 4 / 3 | |
| 2.1.11 | 4 / 3 | |
| 2.1.6 | 4 / 3 | |
| 2.1.1 | 4 / 3 | |
| 1.7.7 | 3 / 3 | |
| 1.7.5 | 3 / 3 | |
| 1.7.4 | 3 / 3 | |
| 1.7.3 | 3 / 3 | |
| 1.7.2 | 3 / 3 |
v2.1.14
2 findingsPackage name '@buoy-gg/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.13
2 findingsPackage name '@buoy-gg/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.12
2 findingsPackage name '@buoy-gg/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.11
2 findingsPackage name '@buoy-gg/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lovesworking.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lovesworking.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.