@goldstack/template-dynamodb-cli
Utilities for building modules for DynamoDB access.
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-config | AI (dependencies): First-party goldstack monorepo package; stable false positive. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-cli | AI (dependencies): First-party goldstack monorepo package; stable false positive. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-log | AI (dependencies): First-party goldstack monorepo package; stable false positive. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-package | AI (dependencies): First-party goldstack monorepo package; stable false positive. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-sh | AI (dependencies): First-party goldstack monorepo package; stable false positive for this org's packages. | ai | |
| provenance | no-provenance | AI (provenance): Goldstack monorepo consistently publishes without Sigstore provenance; stable pattern across 134 versions. | ai | |
| phantom-deps | phantom-dep:@goldstack/utils-log | AI (phantom-deps): Same-org scope; likely re-exported or used transitively within the monorepo build. | ai | |
| phantom-deps | phantom-dep:source-map-support | AI (phantom-deps): source-map-support is a declared runtime dep used via require at startup in compiled TS projects; not a phantom dep. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.6.94 | 12 / 10 | |
| 0.6.92 | 12 / 10 | |
| 0.6.91 | 12 / 10 | |
| 0.6.87 | 12 / 10 | |
| 0.6.86 | 12 / 10 | |
| 0.6.85 | 12 / 10 | |
| 0.6.84 | 12 / 10 | |
| 0.6.77 | 12 / 10 | |
| 0.6.73 | 12 / 10 | |
| 0.6.71 | 12 / 10 | |
| 0.6.68 | 12 / 12 | |
| 0.6.67 | 12 / 12 | |
| 0.6.66 | 12 / 12 | |
| 0.6.64 | 12 / 12 | |
| 0.6.62 | 12 / 12 | |
| 0.6.58 | 11 / 12 | |
| 0.6.56 | 11 / 12 | |
| 0.6.55 | 11 / 12 | |
| 0.6.51 | 11 / 12 | |
| 0.6.49 | 11 / 12 | |
| 0.6.48 | 11 / 12 | |
| 0.6.47 | 11 / 12 | |
| 0.6.44 | 11 / 12 |
v0.6.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.