← Home

@aws-amplify/amplify-nodejs-function-template-provider

npm Repository

Node JS templates supplied by the Amplify Team

6
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

amzn-ossaws-amplify-opsamplify-studio-uibuilderamplify-codegenamplify-data-dev-npmaws-amplify-data-runtime

Keywords

awsamplifylambdanodejs

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@aws-amplify/amplify-cli-core AI (dependencies): First-party AWS Amplify package; stable dependency for this package. ai
dependencies unvetted-dep:@aws-amplify/amplify-prompts AI (dependencies): First-party AWS Amplify package; stable dependency for this package. ai
dependencies unvetted-dep:graphql-transformer-core AI (dependencies): AWS Amplify ecosystem package; expected dependency for this template provider. ai
provenance no-provenance AI (provenance): AWS Amplify CLI monorepo packages consistently lack Sigstore provenance; stable false positive for this publisher. ai

Versions (showing 6 of 6)

Version Deps Published
2.10.20 5 / 3
2.10.19 5 / 3
2.10.18 5 / 3
2.10.17 5 / 3
2.10.16 5 / 3
2.10.15 5 / 3

v2.10.20

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.

v2.10.19

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.

v2.10.18

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.

v2.10.17

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.

v2.10.16

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.

v2.10.15

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.