@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, 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@goldstack/utils-package-config | AI (dependencies): Same-org goldstack sibling package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-git | AI (dependencies): Same-org goldstack sibling package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-config | AI (dependencies): Same-org goldstack sibling package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-aws-cli | AI (dependencies): Same-org goldstack sibling package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-package | AI (dependencies): Same-org goldstack sibling package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-template | AI (dependencies): Same-org goldstack sibling package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-s3-deployment | AI (dependencies): Same-org goldstack sibling package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@goldstack/infra | AI (dependencies): Same-org goldstack sibling package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@goldstack/infra-aws | AI (dependencies): Same-org goldstack sibling package; stable pattern across all versions. | ai | |
| 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:@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 | |
| 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 |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 0.5.100 | 18 / 11 | |
| 0.5.99 | 18 / 11 | |
| 0.5.98 | 18 / 11 | |
| 0.5.97 | 18 / 11 | |
| 0.5.96 | 18 / 11 | |
| 0.5.95 | 18 / 11 | |
| 0.5.93 | 18 / 11 | |
| 0.5.92 | 18 / 11 | |
| 0.5.91 | 18 / 11 | |
| 0.5.90 | 18 / 11 | |
| 0.5.89 | 18 / 11 | |
| 0.5.88 | 18 / 11 | |
| 0.5.86 | 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 | |
| 0.5.52 | 18 / 12 | |
| 0.5.51 | 18 / 12 | |
| 0.5.50 | 18 / 12 | |
| 0.5.49 | 18 / 12 | |
| 0.5.48 | 18 / 12 | |
| 0.5.47 | 18 / 12 | |
| 0.5.46 | 18 / 12 | |
| 0.5.45 | 18 / 12 | |
| 0.5.44 | 18 / 12 | |
| 0.5.43 | 18 / 12 | |
| 0.5.42 | 18 / 12 | |
| 0.5.41 | 18 / 12 | |
| 0.5.40 | 18 / 12 | |
| 0.5.39 | 18 / 12 | |
| 0.5.38 | 18 / 12 | |
| 0.5.37 | 18 / 12 | |
| 0.5.36 | 18 / 12 | |
| 0.5.35 | 18 / 12 | |
| 0.5.34 | 18 / 12 | |
| 0.5.33 | 18 / 12 | |
| 0.5.32 | 18 / 12 | |
| 0.5.31 | 18 / 12 |
v0.5.100
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.99
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.98
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.97
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.