@goldstack/template-dynamodb
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:dynamo-db-local | AI (dependencies): DynamoDB local testing utility; expected dependency for a DynamoDB template package. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-package | AI (dependencies): Same-monorepo sibling package; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-package-config-embedded | AI (dependencies): Same-monorepo sibling package; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@goldstack/infra | AI (dependencies): Same-monorepo sibling package; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-sh | AI (dependencies): Same-monorepo sibling package; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@goldstack/infra-aws | AI (dependencies): Same-monorepo sibling package; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-log | AI (dependencies): Same-monorepo sibling package; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-esbuild | AI (dependencies): Same-monorepo sibling package; stable false positive for this package family. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 137 versions; lack of provenance is consistent with its history. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/types | AI (phantom-deps): Type-only peer dep; not directly imported but legitimately declared for type resolution. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.4.20 | 16 / 12 | |
| 0.4.19 | 16 / 12 | |
| 0.4.17 | 16 / 12 | |
| 0.4.15 | 16 / 12 | |
| 0.4.13 | 16 / 12 | |
| 0.4.5 | 16 / 12 | |
| 0.4.4 | 16 / 12 | |
| 0.4.1 | 16 / 12 | |
| 0.3.70 | 16 / 12 | |
| 0.3.67 | 16 / 13 | |
| 0.3.55 | 16 / 15 | |
| 0.3.53 | 16 / 15 | |
| 0.3.52 | 16 / 15 | |
| 0.3.49 | 16 / 15 | |
| 0.3.48 | 16 / 15 | |
| 0.3.43 | 16 / 15 | |
| 0.3.42 | 16 / 15 |
v0.4.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.19
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.4.17
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.4.15
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.4.13
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.4.5
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.4.4
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.4.1
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.3.70
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.3.67
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.3.55
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.3.53
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.3.52
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.3.49
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.3.48
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.3.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.3.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.