@emartech/escher-request
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:escher-auth | AI (dependencies): escher-auth is the core auth library this package is explicitly designed to wrap; its presence is expected across all versions. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 23.1.6 | 4 / 20 | |
| 23.1.4 | 4 / 20 | |
| 23.1.3 | 4 / 20 | |
| 23.1.2 | 4 / 20 | |
| 23.1.1 | 4 / 20 | |
| 23.0.0 | 4 / 20 |
v23.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v23.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v23.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v23.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v23.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v23.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.