@opentelemetry/resource-detector-container
Opentelemetry resource detector to get container resource attributes
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from individual to GitHub Actions CI/CD is expected for opentelemetry-js-contrib. | ai |
Versions (showing 51 of 54)
| Version | Deps | Published |
|---|---|---|
| 0.8.12 | 2 / 4 | |
| 0.8.11 | 2 / 4 | |
| 0.8.10 | 2 / 4 | |
| 0.8.9 | 2 / 4 | |
| 0.8.8 | 2 / 4 | |
| 0.8.7 | 2 / 4 | |
| 0.8.6 | 2 / 4 | |
| 0.8.5 | 2 / 4 | |
| 0.8.4 | 2 / 4 | |
| 0.8.3 | 2 / 4 | |
| 0.8.2 | 2 / 4 | |
| 0.8.1 | 2 / 4 | |
| 0.8.0 | 2 / 4 | |
| 0.7.11 | 2 / 12 | |
| 0.7.10 | 2 / 12 | |
| 0.7.9 | 2 / 13 | |
| 0.7.8 | 2 / 13 | |
| 0.7.7 | 2 / 13 | |
| 0.7.5 | 3 / 13 | |
| 0.7.4 | 3 / 13 | |
| 0.7.3 | 3 / 13 | |
| 0.7.2 | 3 / 13 | |
| 0.7.1 | 3 / 13 | |
| 0.7.0 | 3 / 13 | |
| 0.6.1 | 3 / 12 | |
| 0.6.0 | 3 / 12 | |
| 0.5.3 | 3 / 12 | |
| 0.5.2 | 3 / 12 | |
| 0.5.1 | 3 / 12 | |
| 0.5.0 | 3 / 11 | |
| 0.4.4 | 3 / 13 | |
| 0.4.3 | 3 / 13 | |
| 0.4.2 | 2 / 13 | |
| 0.4.1 | 2 / 13 | |
| 0.4.0 | 2 / 13 | |
| 0.3.11 | 2 / 13 | |
| 0.3.10 | 2 / 13 | |
| 0.3.9 | 2 / 13 | |
| 0.3.8 | 2 / 13 | |
| 0.3.7 | 2 / 13 | |
| 0.3.6 | 2 / 13 | |
| 0.3.5 | 2 / 13 | |
| 0.3.4 | 2 / 13 | |
| 0.3.3 | 2 / 13 | |
| 0.3.2 | 2 / 13 | |
| 0.3.1 | 2 / 13 | |
| 0.3.0 | 3 / 13 | |
| 0.2.5 | 2 / 13 | |
| 0.2.4 | 2 / 13 | |
| 0.2.3 | 2 / 14 | |
| 0.2.2 | 2 / 14 |
v0.8.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.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.6.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.6.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.5.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.5.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.5.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.5.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.4.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.4.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.4.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.4.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.4.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.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
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.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.