@goatlab/js-utils
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Metadata gap from manual publish, no behavioral indicator; stable publisher history. | ai | |
| dependencies | unvetted-dep:bigint-polyfill | AI (dependencies): Small polyfill lib, plausible for bigint support, no install-time execution risk. | ai | |
| phantom-deps | phantom-dep:keyv | AI (phantom-deps): Used via config, common false positive pattern. | ai | |
| phantom-deps | phantom-dep:bigint-polyfill | AI (phantom-deps): Likely used transitively/via config; not a real concern. | ai | |
| dependencies | unvetted-dep:@toss/ky | AI (dependencies): @toss/ky is a legitimate Toss-maintained ky wrapper; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@lukeed/uuid | AI (dependencies): @lukeed/uuid is a popular, reputable UUID library by Luke Edwards; not a security risk for this package. | ai | |
| dependencies | unvetted-dep:typed-path | AI (dependencies): typed-path is a legitimate, well-known TypeScript utility for type-safe path access; not a security risk for this package. | ai |
Versions (showing 59 of 59)
| Version | Deps | Published |
|---|---|---|
| 0.10.3 | 3 / 16 | |
| 0.10.2 | 3 / 16 | |
| 0.10.1 | 3 / 16 | |
| 0.10.0 | 3 / 16 | |
| 0.9.0 | 3 / 16 | |
| 0.8.42 | 3 / 20 | |
| 0.8.41 | 3 / 20 | |
| 0.8.40 | 3 / 20 | |
| 0.8.39 | 3 / 20 | |
| 0.8.38 | 3 / 20 | |
| 0.8.37 | 5 / 13 | |
| 0.8.36 | 3 / 13 | |
| 0.8.35 | 3 / 13 | |
| 0.8.34 | 3 / 13 | |
| 0.8.33 | 3 / 12 | |
| 0.8.32 | 3 / 12 | |
| 0.8.31 | 3 / 12 | |
| 0.8.30 | 6 / 12 | |
| 0.8.29 | 6 / 12 | |
| 0.8.28 | 7 / 12 | |
| 0.8.27 | 6 / 12 | |
| 0.8.26 | 6 / 12 | |
| 0.8.25 | 6 / 12 | |
| 0.8.24 | 6 / 12 | |
| 0.8.23 | 6 / 12 | |
| 0.8.22 | 6 / 12 | |
| 0.8.21 | 6 / 12 | |
| 0.8.20 | 6 / 12 | |
| 0.8.19 | 6 / 12 | |
| 0.8.18 | 6 / 12 | |
| 0.8.17 | 6 / 12 | |
| 0.8.16 | 6 / 12 | |
| 0.8.15 | 6 / 12 | |
| 0.8.14 | 6 / 12 | |
| 0.8.13 | 6 / 12 | |
| 0.8.12 | 6 / 12 | |
| 0.8.11 | 6 / 12 | |
| 0.8.10 | 6 / 12 | |
| 0.8.9 | 6 / 12 | |
| 0.8.8 | 7 / 12 | |
| 0.8.7 | 7 / 12 | |
| 0.8.6 | 7 / 12 | |
| 0.8.3 | 7 / 12 | |
| 0.8.2 | 7 / 12 | |
| 0.8.1 | 7 / 12 | |
| 0.8.0 | 7 / 12 | |
| 0.7.11 | 7 / 23 | |
| 0.7.10 | 7 / 23 | |
| 0.7.9 | 7 / 23 | |
| 0.7.8 | 7 / 23 | |
| 0.7.7 | 7 / 23 | |
| 0.7.6 | 7 / 23 | |
| 0.7.5 | 7 / 23 | |
| 0.7.4 | 2 / 23 | |
| 0.7.3 | 2 / 23 | |
| 0.7.2 | 2 / 23 | |
| 0.7.1 | 2 / 23 | |
| 0.7.0 | 2 / 23 | |
| 0.6.0 | 2 / 23 |
v0.8.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
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: cabrerabywaters.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
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: cabrerabywaters.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.