← Home

@aws/lambda-invoke-store

npm Repository Homepage

Invoke scoped data storage for AWS Lambda Node.js Runtime Environment

9
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

nosovskyaws-sdk-teamamzn-ossaws-sdk-botawsxrayaws-iot-sdkaws-amplify-opszheallanmohit0193rishabh6788weicongssayaligaikawadpeterzhuamazonforrest-not-gumpcaybloodevertonfragaosa-publishbedrock-agentcore-npmamazon-q-cli-botaws-apm-synthetics-npm

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from aws-sdk-bot to GitHub Actions reflects standard AWS CI/CD migration; SLSA attestation confirms legitimate provenance. ai

Versions (showing 9 of 9)

Version Deps Published
0.2.4 0 / 9
0.2.3 0 / 9
0.2.2 0 / 9
0.2.1 0 / 9
0.2.0 0 / 9
0.1.1 0 / 9
0.1.0 0 / 5
0.0.2 0 / 5
0.0.1 0 / 4

v0.2.3

1 finding
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.

v0.2.2

1 finding
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.

v0.2.1

1 finding
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.

v0.2.0

1 finding
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.

v0.1.1

1 finding
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.

v0.1.0

2 findings
HIGH Publisher changed: aws-sdk-bot → GitHub Actions (on 2025-09-11) provenance

This version was published by a different npm account than previous versions on 2025-09-11. This could indicate a legitimate maintainer transition or an account compromise.

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.

v0.0.2

2 findings
HIGH Publisher changed: aws-sdk-bot → GitHub Actions (on 2025-09-09) provenance

This version was published by a different npm account than previous versions on 2025-09-09. This could indicate a legitimate maintainer transition or an account compromise.

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.

v0.0.1

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.