@opentelemetry/instrumentation-aws-lambda
OpenTelemetry instrumentation for AWS Lambda function invocations
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from human publisher to GitHub Actions CI with SLSA attestation is expected for opentelemetry-js-contrib org packages. | ai | |
| phantom-deps | phantom-dep:@types/aws-lambda | AI (phantom-deps): @types/aws-lambda is a type-only dep used for TypeScript declarations, not a runtime import. | ai |
Versions (showing 51 of 75)
| Version | Deps | Published |
|---|---|---|
| 0.73.0 | 4 / 6 | |
| 0.72.0 | 4 / 6 | |
| 0.71.0 | 4 / 6 | |
| 0.70.0 | 3 / 7 | |
| 0.69.0 | 3 / 7 | |
| 0.68.0 | 3 / 7 | |
| 0.67.0 | 3 / 7 | |
| 0.66.0 | 3 / 7 | |
| 0.65.0 | 3 / 7 | |
| 0.64.0 | 3 / 7 | |
| 0.63.0 | 3 / 7 | |
| 0.62.0 | 3 / 7 | |
| 0.61.1 | 3 / 7 | |
| 0.61.0 | 3 / 7 | |
| 0.60.1 | 3 / 7 | |
| 0.60.0 | 3 / 12 | |
| 0.59.0 | 3 / 12 | |
| 0.58.0 | 3 / 12 | |
| 0.57.2 | 3 / 12 | |
| 0.57.1 | 3 / 12 | |
| 0.56.0 | 3 / 12 | |
| 0.55.0 | 3 / 12 | |
| 0.54.1 | 3 / 12 | |
| 0.54.0 | 3 / 12 | |
| 0.53.1 | 3 / 12 | |
| 0.53.0 | 3 / 12 | |
| 0.52.0 | 3 / 12 | |
| 0.51.1 | 3 / 12 | |
| 0.51.0 | 3 / 12 | |
| 0.50.3 | 3 / 12 | |
| 0.50.2 | 3 / 12 | |
| 0.50.1 | 3 / 12 | |
| 0.50.0 | 3 / 12 | |
| 0.49.0 | 3 / 12 | |
| 0.48.0 | 3 / 12 | |
| 0.47.0 | 3 / 12 | |
| 0.46.0 | 4 / 10 | |
| 0.45.0 | 5 / 12 | |
| 0.44.0 | 5 / 12 | |
| 0.43.0 | 5 / 12 | |
| 0.42.0 | 5 / 12 | |
| 0.41.1 | 5 / 12 | |
| 0.41.0 | 5 / 12 | |
| 0.40.0 | 5 / 12 | |
| 0.39.0 | 5 / 12 | |
| 0.38.0 | 5 / 12 | |
| 0.37.4 | 5 / 12 | |
| 0.37.3 | 5 / 12 | |
| 0.37.2 | 5 / 12 | |
| 0.37.1 | 5 / 12 | |
| 0.37.0 | 5 / 12 |
v0.73.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.72.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.51.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.50.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.50.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.50.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.50.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.49.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.48.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.47.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.46.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.45.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.44.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.43.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.