@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, 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@goatlab/js-utils | AI (phantom-deps): Same-org scoped dependency; used indirectly through build/dev scripts. | ai | |
| phantom-deps | phantom-dep:verror | AI (phantom-deps): Utility dependency; used indirectly through build/dev scripts. | ai | |
| phantom-deps | phantom-dep:shelljs | AI (phantom-deps): CLI utility dependency; used indirectly through build/dev scripts. | ai | |
| phantom-deps | phantom-dep:winston | AI (phantom-deps): Logging utility; used indirectly through build/dev scripts. | ai | |
| phantom-deps | phantom-dep:inquirer | AI (phantom-deps): CLI utility dependency; used indirectly through build/dev scripts. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): CLI utility dependency; used indirectly through build/dev scripts. | ai | |
| phantom-deps | phantom-dep:dockerode | AI (phantom-deps): Utility dependency; used indirectly through build/dev scripts. | ai | |
| phantom-deps | phantom-dep:cli-progress | AI (phantom-deps): CLI utility dependency; used indirectly through build/dev scripts. | ai | |
| phantom-deps | phantom-dep:jsonwebtoken | AI (phantom-deps): Utility dependency; used indirectly through build/dev scripts. | ai | |
| phantom-deps | phantom-dep:fs | AI (phantom-deps): Built-in module; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:ora | AI (phantom-deps): CLI utility dependency; used indirectly through build/dev scripts. | ai | |
| phantom-deps | phantom-dep:colors | AI (phantom-deps): CLI utility dependency; used indirectly through build/dev scripts. | ai | |
| phantom-deps | phantom-dep:figlet | AI (phantom-deps): CLI utility dependency; used indirectly through build/dev scripts. | ai | |
| phantom-deps | phantom-dep:rimraf | AI (phantom-deps): Build utility; used in prebuild/prestart/predev scripts. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Trusted publisher track record; no malicious change accompanies the dormancy. | ai | |
| provenance | missing-githead | AI (provenance): No code diff vs prior approved version; benign publish-tooling variance. | ai | |
| 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 81 of 81)
| 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.53 | 12 / 13 | |
| 0.8.52 | 12 / 13 | |
| 0.8.51 | 12 / 13 | |
| 0.8.50 | 13 / 13 | |
| 0.8.49 | 13 / 13 | |
| 0.8.48 | 21 / 12 | |
| 0.8.45 | 19 / 12 | |
| 0.8.44 | 19 / 12 | |
| 0.8.43 | 19 / 12 | |
| 0.8.42 | 19 / 12 | |
| 0.8.41 | 19 / 12 | |
| 0.8.40 | 19 / 12 | |
| 0.8.39 | 19 / 12 | |
| 0.8.38 | 19 / 12 | |
| 0.8.37 | 19 / 12 | |
| 0.8.36 | 19 / 12 | |
| 0.8.35 | 19 / 12 | |
| 0.8.34 | 19 / 12 | |
| 0.8.33 | 19 / 12 | |
| 0.8.32 | 18 / 12 | |
| 0.8.31 | 18 / 12 | |
| 0.8.30 | 18 / 12 | |
| 0.8.29 | 18 / 12 | |
| 0.8.28 | 18 / 12 | |
| 0.8.27 | 18 / 12 | |
| 0.8.26 | 18 / 12 | |
| 0.8.25 | 18 / 12 | |
| 0.8.24 | 19 / 12 | |
| 0.8.23 | 19 / 12 | |
| 0.8.22 | 19 / 12 | |
| 0.8.21 | 19 / 12 | |
| 0.8.20 | 19 / 12 | |
| 0.8.19 | 19 / 12 | |
| 0.8.18 | 19 / 12 | |
| 0.8.17 | 19 / 12 | |
| 0.8.16 | 19 / 12 | |
| 0.8.15 | 19 / 12 | |
| 0.8.14 | 20 / 12 | |
| 0.8.13 | 20 / 12 | |
| 0.8.12 | 20 / 12 | |
| 0.8.11 | 18 / 12 | |
| 0.8.10 | 18 / 12 | |
| 0.8.9 | 18 / 12 | |
| 0.8.8 | 18 / 12 | |
| 0.8.7 | 14 / 12 | |
| 0.8.6 | 14 / 12 | |
| 0.8.5 | 14 / 12 | |
| 0.8.4 | 13 / 12 | |
| 0.8.3 | 13 / 12 | |
| 0.8.2 | 13 / 12 | |
| 0.8.1 | 17 / 12 | |
| 0.8.0 | 17 / 12 | |
| 0.7.8 | 17 / 23 | |
| 0.7.7 | 17 / 23 | |
| 0.7.6 | 17 / 23 | |
| 0.7.5 | 17 / 23 | |
| 0.7.4 | 17 / 23 | |
| 0.7.3 | 17 / 23 | |
| 0.7.2 | 17 / 23 | |
| 0.7.1 | 17 / 23 | |
| 0.7.0 | 17 / 23 | |
| 0.6.1 | 17 / 23 |
v0.8.53
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.51
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.50
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.