@goldstack/utils-terraform-aws
Easily deploy Terraform IaC with 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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established goldstack monorepo package; provenance not used across the org, stable pattern. | ai | |
| phantom-deps | phantom-dep:@goldstack/utils-sh | AI (phantom-deps): Same-org sibling dep; re-exported rather than directly imported, stable FP for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@goldstack/utils-cli | AI (phantom-deps): Same-org sibling dep; stable FP for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@goldstack/utils-config | AI (phantom-deps): Same-org sibling dep; stable FP for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@goldstack/utils-package | AI (phantom-deps): Same-org sibling dep; stable FP for this monorepo package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.4.92 | 10 / 7 | |
| 0.4.90 | 10 / 7 | |
| 0.4.89 | 10 / 7 | |
| 0.4.85 | 10 / 7 | |
| 0.4.78 | 10 / 7 | |
| 0.4.75 | 10 / 7 | |
| 0.4.72 | 10 / 7 | |
| 0.4.71 | 10 / 7 | |
| 0.4.69 | 10 / 8 | |
| 0.4.68 | 10 / 8 | |
| 0.4.64 | 10 / 8 | |
| 0.4.63 | 10 / 8 | |
| 0.4.60 | 10 / 8 | |
| 0.4.59 | 10 / 8 | |
| 0.4.56 | 10 / 8 |
v0.4.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.89
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.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.75
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.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.69
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.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.63
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.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.