← Home

@iyio/aws-lambda

npm

This library was generated with [Nx](https://nx.dev).

38
Versions
—
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

iyio

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Scoped monorepo package with 62 versions and 1126-day history; sparse metadata is a consistent pattern, not spam. ai

Versions (showing 38 of 38)

Version Deps Published
0.9.6 0 / 0
0.9.1 0 / 0
0.8.18 0 / 0
0.8.17 0 / 0
0.8.11 0 / 0
0.8.1 0 / 0
0.8.0 0 / 0
0.7.50 0 / 0
0.7.43 0 / 0
0.7.42 0 / 0
0.7.37 0 / 0
0.7.36 0 / 0
0.7.34 0 / 0
0.7.33 0 / 0
0.7.31 0 / 0
0.7.29 0 / 0
0.7.28 0 / 0
0.7.24 0 / 0
0.7.23 0 / 0
0.7.22 0 / 0
0.7.19 0 / 0
0.7.17 0 / 0
0.7.15 0 / 0
0.7.14 0 / 0
0.7.13 0 / 0
0.7.12 0 / 0
0.7.11 0 / 0
0.7.10 0 / 0
0.7.9 0 / 0
0.7.7 0 / 0
0.7.6 0 / 0
0.7.5 0 / 0
0.7.2 0 / 0
0.7.0 0 / 0
0.6.5 0 / 0
0.6.4 0 / 0
0.6.3 0 / 0
0.6.0 0 / 0

v0.7.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.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.