@goldstack/utils-terraform-hetzner
Easily deploy Terraform IaC with npm package scripts for Hetzner Cloud Services
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@goldstack/utils-sh | AI (phantom-deps): Same-org monorepo sibling; phantom-dep is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@goldstack/utils-log | AI (phantom-deps): Same-org monorepo sibling; phantom-dep is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@goldstack/utils-config | AI (phantom-deps): Same-org monorepo sibling; phantom-dep is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@goldstack/utils-package | AI (phantom-deps): Same-org monorepo sibling; phantom-dep is a stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established goldstack monorepo package; no provenance is consistent across all versions. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.1.71 | 7 / 7 | |
| 0.1.70 | 7 / 7 | |
| 0.1.68 | 7 / 7 | |
| 0.1.67 | 7 / 7 | |
| 0.1.66 | 7 / 7 | |
| 0.1.65 | 7 / 7 | |
| 0.1.62 | 7 / 7 | |
| 0.1.60 | 7 / 7 | |
| 0.1.59 | 7 / 7 | |
| 0.1.58 | 7 / 7 | |
| 0.1.57 | 7 / 7 | |
| 0.1.56 | 7 / 7 | |
| 0.1.47 | 7 / 8 | |
| 0.1.45 | 7 / 8 | |
| 0.1.44 | 7 / 8 | |
| 0.1.43 | 7 / 8 | |
| 0.1.42 | 7 / 8 | |
| 0.1.41 | 7 / 8 | |
| 0.1.37 | 7 / 8 | |
| 0.1.36 | 7 / 8 | |
| 0.1.35 | 7 / 8 |
v0.1.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.60
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.1.59
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.1.58
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.1.57
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.1.56
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.1.47
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.1.45
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.1.44
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.1.43
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.1.42
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.1.41
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.1.37
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.1.36
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.1.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.