@opentelemetry/instrumentation-express
OpenTelemetry instrumentation for `express` http web application framework
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): OpenTelemetry JS Contrib migrated to GitHub Actions CI/CD publishing with SLSA provenance. Publisher change from human account to GitHub Actions is the expected and documented transition for this project. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Large version jump (0.47.1→0.63.0) suggests prior versions published under different tracking. Official OTel monorepo package with SLSA attestation; dormancy signal is a false positive here. | ai |
Versions (showing 51 of 74)
| Version | Deps | Published |
|---|---|---|
| 0.69.0 | 3 / 6 | |
| 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.0 | 3 / 7 | |
| 0.60.0 | 3 / 7 | |
| 0.59.0 | 3 / 7 | |
| 0.58.0 | 3 / 7 | |
| 0.57.1 | 3 / 7 | |
| 0.57.0 | 3 / 15 | |
| 0.56.0 | 3 / 15 | |
| 0.55.0 | 3 / 15 | |
| 0.54.3 | 3 / 15 | |
| 0.54.2 | 3 / 15 | |
| 0.54.0 | 3 / 15 | |
| 0.53.0 | 3 / 15 | |
| 0.52.0 | 3 / 15 | |
| 0.51.1 | 3 / 15 | |
| 0.51.0 | 3 / 15 | |
| 0.50.0 | 3 / 15 | |
| 0.49.0 | 3 / 15 | |
| 0.48.1 | 3 / 15 | |
| 0.48.0 | 3 / 15 | |
| 0.47.1 | 3 / 15 | |
| 0.47.0 | 3 / 15 | |
| 0.46.0 | 3 / 15 | |
| 0.45.0 | 3 / 15 | |
| 0.44.0 | 3 / 15 | |
| 0.43.0 | 3 / 17 | |
| 0.42.0 | 3 / 17 | |
| 0.41.1 | 3 / 17 | |
| 0.41.0 | 3 / 17 | |
| 0.40.1 | 3 / 17 | |
| 0.40.0 | 3 / 17 | |
| 0.39.0 | 3 / 17 | |
| 0.38.0 | 3 / 17 | |
| 0.37.0 | 3 / 17 | |
| 0.36.1 | 3 / 17 | |
| 0.36.0 | 3 / 17 | |
| 0.35.0 | 3 / 16 | |
| 0.34.1 | 3 / 16 | |
| 0.34.0 | 3 / 16 | |
| 0.33.3 | 4 / 15 | |
| 0.33.2 | 4 / 15 | |
| 0.33.1 | 4 / 15 | |
| 0.33.0 | 5 / 15 | |
| 0.32.4 | 4 / 15 |
v0.69.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.68.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.48.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.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 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.41.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.41.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.40.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.