@opentelemetry/instrumentation-fastify
OpenTelemetry instrumentation for `fastify` 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 publishing; SLSA provenance attestation confirms legitimate CI origin. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects monorepo release cadence, not account takeover; SLSA attestation and org repo URL confirm legitimacy. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 0.57.0 | 3 / 8 | |
| 0.56.0 | 3 / 8 | |
| 0.55.0 | 3 / 8 | |
| 0.54.0 | 3 / 8 | |
| 0.53.1 | 3 / 8 | |
| 0.53.0 | 3 / 16 | |
| 0.52.0 | 3 / 16 | |
| 0.51.0 | 3 / 16 | |
| 0.50.3 | 3 / 16 | |
| 0.50.2 | 3 / 16 | |
| 0.50.0 | 3 / 16 | |
| 0.49.0 | 3 / 16 | |
| 0.48.0 | 3 / 17 | |
| 0.47.1 | 3 / 17 | |
| 0.47.0 | 3 / 17 | |
| 0.46.0 | 3 / 17 | |
| 0.45.0 | 3 / 17 | |
| 0.44.2 | 3 / 17 | |
| 0.44.1 | 3 / 17 | |
| 0.44.0 | 3 / 17 | |
| 0.43.0 | 3 / 17 | |
| 0.42.0 | 3 / 17 | |
| 0.41.0 | 3 / 17 | |
| 0.40.0 | 3 / 19 | |
| 0.39.0 | 3 / 19 | |
| 0.38.0 | 3 / 19 | |
| 0.37.0 | 3 / 19 | |
| 0.36.1 | 3 / 19 | |
| 0.36.0 | 3 / 19 | |
| 0.35.0 | 3 / 19 | |
| 0.34.0 | 3 / 19 | |
| 0.33.0 | 3 / 19 | |
| 0.32.6 | 3 / 19 | |
| 0.32.5 | 3 / 19 | |
| 0.32.4 | 3 / 16 | |
| 0.32.3 | 3 / 16 | |
| 0.32.2 | 3 / 15 | |
| 0.32.1 | 3 / 15 | |
| 0.32.0 | 4 / 15 | |
| 0.31.4 | 3 / 15 | |
| 0.31.3 | 3 / 15 | |
| 0.31.2 | 3 / 16 | |
| 0.31.1 | 3 / 16 | |
| 0.31.0 | 3 / 16 | |
| 0.30.1 | 3 / 16 | |
| 0.30.0 | 4 / 15 | |
| 0.29.0 | 4 / 15 | |
| 0.28.0 | 4 / 15 | |
| 0.27.0 | 4 / 15 | |
| 0.26.0 | 4 / 15 | |
| 0.25.0 | 4 / 16 |
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.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.44.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.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.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.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.39.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.38.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.0
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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.5
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.
v0.32.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.