@telnyx/webrtc
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is a declared runtime dependency; phantom-dep heuristic misfires for this package. | ai | |
| phantom-deps | phantom-dep:@peermetrics/webrtc-stats | AI (phantom-deps): @peermetrics/webrtc-stats is a declared runtime dependency; phantom-dep heuristic misfires for this package. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 2.27.8 | 3 / 30 | |
| 2.27.7 | 3 / 30 | |
| 2.27.6 | 3 / 30 | |
| 2.27.5 | 3 / 30 | |
| 2.27.4 | 3 / 30 | |
| 2.27.3 | 3 / 30 | |
| 2.27.2 | 3 / 30 | |
| 2.27.1 | 3 / 30 | |
| 2.26.4 | 3 / 30 | |
| 2.26.3 | 3 / 30 | |
| 2.26.2 | 3 / 30 | |
| 2.26.1 | 3 / 30 | |
| 2.25.15 | 3 / 30 | |
| 2.24.1 | 3 / 32 | |
| 2.24.0 | 3 / 32 | |
| 2.22.19 | 3 / 32 | |
| 2.22.18 | 3 / 32 | |
| 2.22.17 | 3 / 32 | |
| 2.22.16 | 3 / 32 | |
| 2.22.15 | 3 / 32 | |
| 2.22.14 | 3 / 32 | |
| 2.22.13 | 3 / 32 | |
| 2.22.12 | 3 / 32 | |
| 2.22.11 | 3 / 32 | |
| 2.22.10 | 3 / 32 | |
| 2.22.9 | 3 / 32 | |
| 2.22.8 | 3 / 32 | |
| 2.22.7 | 3 / 32 | |
| 2.22.6 | 3 / 32 | |
| 2.22.5 | 3 / 32 | |
| 2.22.4 | 3 / 32 | |
| 2.22.3 | 3 / 32 | |
| 2.22.2 | 3 / 32 | |
| 2.22.1 | 3 / 32 | |
| 2.22.0 | 3 / 33 | |
| 2.21.2 | 3 / 33 | |
| 2.21.1 | 3 / 33 | |
| 2.21.0 | 3 / 33 | |
| 2.20.0 | 3 / 33 | |
| 2.19.0 | 3 / 33 | |
| 2.18.0 | 3 / 33 | |
| 2.17.0 | 3 / 33 | |
| 2.16.0 | 3 / 33 |
v2.27.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.27.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.27.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.27.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.27.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.27.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.27.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.22.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.