@goat-sdk/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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped SDK package @goat-sdk/core; Levenshtein match to 'cors' is coincidental, not a typosquat. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.5.0 | 1 / 1 | |
| 0.3.11 | 4 / 0 | |
| 0.3.4 | 4 / 6 | |
| 0.3.1 | 4 / 6 | |
| 0.3.0 | 4 / 6 |
v0.3.11
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mpaella.
This version was published by a different npm account than previous versions on 2024-12-09. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.