@opentelemetry/instrumentation-dataloader
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 legitimate automated release. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 0.38.0 | 1 / 5 | |
| 0.37.0 | 1 / 6 | |
| 0.36.0 | 1 / 6 | |
| 0.35.0 | 1 / 6 | |
| 0.34.0 | 1 / 6 | |
| 0.33.0 | 1 / 6 | |
| 0.32.0 | 1 / 6 | |
| 0.31.0 | 1 / 6 | |
| 0.30.0 | 1 / 6 | |
| 0.29.0 | 1 / 6 | |
| 0.28.0 | 1 / 6 | |
| 0.27.0 | 1 / 6 | |
| 0.26.1 | 1 / 6 | |
| 0.26.0 | 1 / 12 | |
| 0.25.0 | 1 / 12 | |
| 0.24.0 | 1 / 12 | |
| 0.23.3 | 1 / 12 | |
| 0.23.2 | 1 / 12 | |
| 0.23.0 | 1 / 12 | |
| 0.22.0 | 1 / 12 | |
| 0.21.1 | 1 / 12 | |
| 0.21.0 | 1 / 11 | |
| 0.20.0 | 1 / 11 | |
| 0.19.0 | 1 / 11 | |
| 0.18.0 | 1 / 11 | |
| 0.17.0 | 1 / 11 | |
| 0.16.1 | 1 / 11 | |
| 0.16.0 | 1 / 11 | |
| 0.15.0 | 1 / 11 | |
| 0.14.0 | 1 / 11 | |
| 0.13.0 | 1 / 11 | |
| 0.12.0 | 1 / 13 | |
| 0.11.0 | 1 / 13 | |
| 0.10.0 | 1 / 13 | |
| 0.9.0 | 1 / 13 | |
| 0.8.0 | 1 / 13 | |
| 0.7.0 | 1 / 13 | |
| 0.6.0 | 1 / 13 | |
| 0.5.4 | 1 / 13 | |
| 0.5.3 | 1 / 13 | |
| 0.5.2 | 1 / 13 | |
| 0.5.1 | 1 / 13 | |
| 0.5.0 | 2 / 13 | |
| 0.4.3 | 1 / 13 | |
| 0.4.2 | 1 / 13 | |
| 0.4.1 | 1 / 14 | |
| 0.4.0 | 1 / 14 | |
| 0.3.1 | 1 / 14 | |
| 0.3.0 | 1 / 14 | |
| 0.2.1 | 1 / 14 | |
| 0.2.0 | 1 / 14 |
v0.38.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.37.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.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.16.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.16.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.15.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.14.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.13.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.12.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.11.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.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.