@goatlab/node-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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package with long history; lack of provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:child_process | AI (phantom-deps): child_process is a Node built-in listed as a nominal dep; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:http-errors | AI (phantom-deps): http-errors is a common utility dep; phantom-dep heuristic fires but it's a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@types/through2-concurrent | AI (phantom-deps): Type-only package loaded by convention; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:path | AI (phantom-deps): path is a Node.js built-in polyfill commonly declared as a dependency in TypeScript projects; not directly imported in source is expected behavior. | ai | |
| phantom-deps | phantom-dep:@goatlab/tsconfig | AI (phantom-deps): @goatlab/tsconfig is a TypeScript config package used at build time; not being directly imported in source is expected for tsconfig packages. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.11.2 | 11 / 13 | |
| 0.11.1 | 11 / 13 | |
| 0.11.0 | 11 / 13 | |
| 0.10.4 | 11 / 13 | |
| 0.10.3 | 11 / 13 | |
| 0.10.2 | 11 / 13 | |
| 0.10.1 | 11 / 13 | |
| 0.10.0 | 11 / 13 | |
| 0.9.2 | 11 / 13 | |
| 0.9.1 | 11 / 13 | |
| 0.9.0 | 11 / 13 | |
| 0.8.61 | 11 / 13 | |
| 0.8.60 | 11 / 13 | |
| 0.8.59 | 11 / 13 | |
| 0.8.58 | 11 / 13 | |
| 0.8.57 | 11 / 13 | |
| 0.8.56 | 11 / 13 | |
| 0.8.55 | 11 / 13 | |
| 0.8.54 | 11 / 13 | |
| 0.8.52 | 12 / 13 | |
| 0.8.49 | 13 / 13 | |
| 0.8.48 | 21 / 12 |
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.