← Home

dynamodb-tooling

npm Repository Homepage
3
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

chrisbreuer

Keywords

dynamodbutilitiestypescriptbunpackage

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:postinstall AI (install-scripts): git-hooks setup script, matches package's own git-hooks config. ai
semgrep semgrep:base64-decode AI (semgrep): Standard key decoding in Encryption.ts, not payload hiding. ai
semgrep semgrep:new-function-constructor AI (semgrep): Dynamic import workaround for optional dependency, not eval of untrusted input. ai

Versions (showing 3 of 3)

Version Deps Published
0.3.4 0 / 10
0.3.2 0 / 16
0.2.0 0 / 16

v0.3.4

4 findings
HIGH Package has 'postinstall' script install-scripts

Script: bunx git-hooks

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: chrisbreuer → GitHub Actions (on 2026-07-14, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (chrisbreuer) on 2026-07-14, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v0.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.