@goldstack/utils-terraform
Run Terraform commands easily as npm package scripts
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@goldstack/utils-package | AI (dependencies): Same-org sibling dependency in the goldstack monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-log | AI (dependencies): Same-org sibling dependency in the goldstack monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-config | AI (dependencies): Same-org sibling dependency in the goldstack monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-docker | AI (dependencies): Same-org sibling dependency in the goldstack monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@goldstack/infra | AI (dependencies): Same-org sibling dependency in the goldstack monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-sh | AI (dependencies): Same-org sibling dependency in the goldstack monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@goldstack/infra-aws | AI (dependencies): Same-org sibling dependency in the goldstack monorepo; stable pattern across all versions. | ai | |
| phantom-deps | phantom-dep:yargs | AI (phantom-deps): yargs is a declared runtime dep used via CLI; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@goldstack/utils-config | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is a stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@goldstack/infra-aws | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is a stable false positive for this monorepo package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.4.87 | 10 / 10 | |
| 0.4.86 | 10 / 10 | |
| 0.4.85 | 10 / 10 | |
| 0.4.84 | 10 / 10 | |
| 0.4.83 | 10 / 10 | |
| 0.4.82 | 10 / 10 | |
| 0.4.81 | 10 / 10 | |
| 0.4.80 | 10 / 10 | |
| 0.4.79 | 10 / 10 | |
| 0.4.77 | 10 / 10 | |
| 0.4.74 | 9 / 10 | |
| 0.4.72 | 9 / 10 | |
| 0.4.68 | 9 / 10 | |
| 0.4.66 | 9 / 11 | |
| 0.4.65 | 9 / 11 | |
| 0.4.62 | 9 / 11 | |
| 0.4.60 | 9 / 11 | |
| 0.4.57 | 9 / 11 | |
| 0.4.55 | 9 / 11 | |
| 0.4.54 | 9 / 11 | |
| 0.4.53 | 9 / 11 | |
| 0.4.52 | 9 / 11 | |
| 0.4.48 | 9 / 11 |
v0.4.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.