@opentelemetry/instrumentation-bunyan
OpenTelemetry instrumentation for `bunyan` logger
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 publishing; SLSA provenance attestation confirms CI-signed release. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects upstream release cadence, not account takeover; SLSA attestation and org repo confirm legitimacy. | ai | |
| phantom-deps | phantom-dep:@types/bunyan | AI (phantom-deps): @types/bunyan is intentionally a runtime dependency in this instrumentation package to provide TypeScript type definitions for consumers; not a true phantom dep. | ai | |
| dependencies | unvetted-dep:@types/bunyan | AI (dependencies): @types/bunyan is a well-known DefinitelyTyped package used for TypeScript type exports; its inclusion as a runtime dep is intentional and stable for this package. | ai |
Versions (showing 60 of 60)
| Version | Deps | Published |
|---|---|---|
| 0.66.0 | 4 / 6 | |
| 0.65.0 | 4 / 6 | |
| 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.0 | 3 / 7 | |
| 0.56.0 | 3 / 7 | |
| 0.55.0 | 3 / 7 | |
| 0.54.0 | 3 / 15 | |
| 0.53.0 | 3 / 15 | |
| 0.52.0 | 3 / 15 | |
| 0.51.4 | 3 / 15 | |
| 0.51.3 | 3 / 15 | |
| 0.51.0 | 3 / 15 | |
| 0.50.0 | 3 / 15 | |
| 0.49.0 | 3 / 15 | |
| 0.48.0 | 3 / 15 | |
| 0.47.0 | 3 / 15 | |
| 0.46.0 | 3 / 15 | |
| 0.45.1 | 3 / 15 | |
| 0.45.0 | 3 / 15 | |
| 0.44.0 | 3 / 15 | |
| 0.43.0 | 3 / 15 | |
| 0.42.0 | 3 / 15 | |
| 0.41.0 | 3 / 17 | |
| 0.40.0 | 3 / 17 | |
| 0.39.0 | 3 / 17 | |
| 0.38.0 | 3 / 17 | |
| 0.37.0 | 3 / 17 | |
| 0.36.0 | 3 / 17 | |
| 0.35.0 | 3 / 17 | |
| 0.34.1 | 3 / 17 | |
| 0.34.0 | 3 / 17 | |
| 0.33.0 | 2 / 15 | |
| 0.32.2 | 2 / 15 | |
| 0.32.1 | 2 / 15 | |
| 0.32.0 | 3 / 15 | |
| 0.31.4 | 2 / 15 | |
| 0.31.3 | 2 / 15 | |
| 0.31.2 | 2 / 16 | |
| 0.31.1 | 2 / 16 | |
| 0.31.0 | 2 / 16 | |
| 0.30.1 | 2 / 16 | |
| 0.30.0 | 2 / 16 | |
| 0.29.0 | 2 / 16 | |
| 0.28.0 | 2 / 16 | |
| 0.27.1 | 2 / 17 | |
| 0.27.0 | 2 / 16 | |
| 0.26.0 | 2 / 16 | |
| 0.25.0 | 2 / 16 | |
| 0.24.0 | 2 / 16 | |
| 0.23.0 | 2 / 16 | |
| 0.22.0 | 2 / 16 | |
| 0.21.0 | 2 / 16 | |
| 0.20.0 | 3 / 15 | |
| 0.16.0 | 2 / 18 |
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.65.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.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.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.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 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.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.0
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.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.