@goldstack/template-docker-image-aws
Utilities for packages that are deployed as Docker Images using AWS Fargate
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): Goldstack monorepo consistently publishes without Sigstore provenance; stable pattern across 228 versions. | ai | |
| phantom-deps | phantom-dep:@goldstack/utils-log | AI (phantom-deps): Same-org sibling dep; phantom-dep false positive stable for this monorepo package. | ai | |
| phantom-deps | phantom-dep:source-map-support | AI (phantom-deps): source-map-support is a declared runtime dep used via require at startup; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@goldstack/utils-config | AI (phantom-deps): Same-org dep; used transitively within the goldstack monorepo. Stable false positive. | ai | |
| phantom-deps | phantom-dep:@goldstack/utils-template | AI (phantom-deps): Same-org dep; used transitively within the goldstack monorepo. Stable false positive. | ai | |
| phantom-deps | phantom-dep:@goldstack/utils-s3-deployment | AI (phantom-deps): Same-org dep; used transitively within the goldstack monorepo. Stable false positive. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.5.95 | 18 / 11 | |
| 0.5.92 | 18 / 11 | |
| 0.5.89 | 18 / 11 | |
| 0.5.88 | 18 / 11 | |
| 0.5.84 | 18 / 11 | |
| 0.5.82 | 18 / 11 | |
| 0.5.81 | 18 / 11 | |
| 0.5.79 | 18 / 11 | |
| 0.5.75 | 18 / 11 | |
| 0.5.71 | 18 / 12 | |
| 0.5.70 | 18 / 12 | |
| 0.5.65 | 18 / 12 | |
| 0.5.64 | 18 / 12 | |
| 0.5.63 | 18 / 12 | |
| 0.5.62 | 18 / 12 | |
| 0.5.60 | 18 / 12 | |
| 0.5.59 | 18 / 12 | |
| 0.5.56 | 18 / 12 | |
| 0.5.54 | 18 / 12 |
v0.5.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.