@opentelemetry/instrumentation-nestjs-core
OpenTelemetry instrumentation for NestJS server side applications 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 attestation confirms official org pipeline. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects monorepo release cadence, not account takeover; SLSA provenance confirms legitimate CI publish. | ai |
Versions (showing 51 of 60)
| Version | Deps | Published |
|---|---|---|
| 0.67.0 | 2 / 9 | |
| 0.66.0 | 2 / 10 | |
| 0.65.0 | 2 / 10 | |
| 0.64.0 | 2 / 10 | |
| 0.63.0 | 2 / 10 | |
| 0.62.0 | 2 / 10 | |
| 0.61.0 | 2 / 10 | |
| 0.60.0 | 2 / 10 | |
| 0.59.0 | 2 / 10 | |
| 0.58.0 | 2 / 10 | |
| 0.57.0 | 2 / 10 | |
| 0.56.0 | 2 / 10 | |
| 0.55.0 | 2 / 19 | |
| 0.54.0 | 2 / 19 | |
| 0.53.0 | 2 / 19 | |
| 0.52.2 | 2 / 19 | |
| 0.52.1 | 2 / 19 | |
| 0.51.0 | 2 / 19 | |
| 0.50.0 | 2 / 19 | |
| 0.49.0 | 2 / 19 | |
| 0.48.1 | 2 / 19 | |
| 0.48.0 | 2 / 19 | |
| 0.47.0 | 2 / 19 | |
| 0.46.0 | 2 / 19 | |
| 0.45.0 | 2 / 19 | |
| 0.44.1 | 2 / 19 | |
| 0.44.0 | 2 / 19 | |
| 0.43.0 | 2 / 18 | |
| 0.42.0 | 2 / 18 | |
| 0.41.0 | 2 / 18 | |
| 0.40.0 | 2 / 23 | |
| 0.39.0 | 2 / 23 | |
| 0.38.0 | 2 / 23 | |
| 0.37.1 | 2 / 23 | |
| 0.37.0 | 2 / 23 | |
| 0.36.0 | 2 / 23 | |
| 0.35.0 | 2 / 23 | |
| 0.34.0 | 2 / 23 | |
| 0.33.4 | 2 / 23 | |
| 0.33.3 | 2 / 23 | |
| 0.33.2 | 2 / 23 | |
| 0.33.1 | 2 / 23 | |
| 0.33.0 | 3 / 23 | |
| 0.32.5 | 2 / 23 | |
| 0.32.4 | 2 / 23 | |
| 0.32.3 | 2 / 24 | |
| 0.32.2 | 2 / 24 | |
| 0.32.1 | 2 / 25 | |
| 0.32.0 | 2 / 25 | |
| 0.31.1 | 2 / 25 | |
| 0.31.0 | 2 / 25 |
v0.67.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.66.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). 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.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 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.4
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.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.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.