@opentelemetry/instrumentation-tedious
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): Moved from individual maintainer to GitHub Actions CI/CD; expected for opentelemetry-js-contrib. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Large monorepo with irregular per-package release cadence; dormancy is normal. | ai | |
| dependencies | unvetted-dep:@types/tedious | AI (dependencies): @types/tedious is a legitimate DefinitelyTyped package providing TypeScript type declarations for the tedious SQL Server client; stable and expected dependency for this instrumentation package. | ai | |
| phantom-deps | phantom-dep:@types/tedious | AI (phantom-deps): @types/* packages are loaded by TypeScript convention, not via explicit imports; phantom-dep finding is a stable false positive for all @types/* dependencies in this package. | ai |
Versions (showing 51 of 55)
| Version | Deps | Published |
|---|---|---|
| 0.40.0 | 3 / 5 | |
| 0.39.0 | 3 / 5 | |
| 0.38.0 | 3 / 5 | |
| 0.37.0 | 3 / 5 | |
| 0.36.0 | 3 / 5 | |
| 0.35.0 | 3 / 5 | |
| 0.34.0 | 3 / 5 | |
| 0.33.0 | 3 / 5 | |
| 0.32.0 | 3 / 5 | |
| 0.31.0 | 3 / 5 | |
| 0.30.0 | 3 / 5 | |
| 0.29.0 | 3 / 5 | |
| 0.28.0 | 3 / 5 | |
| 0.27.0 | 2 / 13 | |
| 0.26.0 | 2 / 13 | |
| 0.25.0 | 2 / 13 | |
| 0.24.3 | 2 / 13 | |
| 0.24.2 | 2 / 13 | |
| 0.24.0 | 3 / 13 | |
| 0.23.0 | 3 / 13 | |
| 0.22.0 | 3 / 12 | |
| 0.21.1 | 3 / 12 | |
| 0.21.0 | 3 / 12 | |
| 0.20.0 | 3 / 12 | |
| 0.19.0 | 3 / 12 | |
| 0.18.1 | 3 / 12 | |
| 0.18.0 | 3 / 12 | |
| 0.17.0 | 3 / 12 | |
| 0.16.0 | 3 / 12 | |
| 0.15.0 | 3 / 12 | |
| 0.14.0 | 3 / 14 | |
| 0.13.0 | 3 / 14 | |
| 0.12.0 | 3 / 14 | |
| 0.11.0 | 3 / 14 | |
| 0.10.1 | 3 / 13 | |
| 0.10.0 | 3 / 13 | |
| 0.9.0 | 3 / 13 | |
| 0.8.0 | 3 / 13 | |
| 0.7.0 | 3 / 13 | |
| 0.6.5 | 3 / 13 | |
| 0.6.4 | 3 / 13 | |
| 0.6.3 | 3 / 13 | |
| 0.6.2 | 3 / 13 | |
| 0.6.1 | 3 / 13 | |
| 0.6.0 | 4 / 13 | |
| 0.5.4 | 3 / 13 | |
| 0.5.3 | 3 / 13 | |
| 0.5.2 | 3 / 14 | |
| 0.5.1 | 3 / 14 | |
| 0.5.0 | 3 / 14 | |
| 0.4.1 | 3 / 14 |
v0.40.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.39.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.19.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.18.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.18.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.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.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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
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.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.