@eik/service
Eik REST API as a standalone HTTP service
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 100 of 116)
| Version | Deps | Published |
|---|---|---|
| 5.1.65 | 12 / 12 | |
| 5.1.64 | 12 / 12 | |
| 5.1.63 | 12 / 12 | |
| 5.1.62 | 12 / 12 | |
| 5.1.61 | 12 / 12 | |
| 5.1.60 | 12 / 12 | |
| 5.1.59 | 12 / 12 | |
| 5.1.58 | 12 / 12 | |
| 5.1.57 | 12 / 12 | |
| 5.1.56 | 12 / 12 | |
| 5.1.55 | 12 / 12 | |
| 5.1.54 | 12 / 12 | |
| 5.1.53 | 12 / 12 | |
| 5.1.52 | 12 / 13 | |
| 5.1.51 | 12 / 17 | |
| 5.1.50 | 12 / 17 | |
| 5.1.49 | 12 / 17 | |
| 5.1.48 | 12 / 17 | |
| 5.1.47 | 12 / 17 | |
| 5.1.46 | 12 / 17 | |
| 5.1.45 | 12 / 17 | |
| 5.1.44 | 12 / 17 | |
| 5.1.43 | 12 / 17 | |
| 5.1.42 | 12 / 17 | |
| 5.1.41 | 12 / 17 | |
| 5.1.40 | 12 / 17 | |
| 5.1.39 | 12 / 17 | |
| 5.1.38 | 12 / 17 | |
| 5.1.37 | 12 / 17 | |
| 5.1.36 | 12 / 17 | |
| 5.1.35 | 12 / 17 | |
| 5.1.34 | 12 / 17 | |
| 5.1.33 | 12 / 17 | |
| 5.1.32 | 12 / 17 | |
| 5.1.31 | 12 / 17 | |
| 5.1.30 | 12 / 17 | |
| 5.1.29 | 12 / 17 | |
| 5.1.28 | 12 / 17 | |
| 5.1.27 | 12 / 17 | |
| 5.1.26 | 12 / 17 | |
| 5.1.25 | 12 / 17 | |
| 5.1.24 | 12 / 17 | |
| 5.1.23 | 12 / 17 | |
| 5.1.22 | 12 / 17 | |
| 5.1.21 | 12 / 17 | |
| 5.1.20 | 12 / 17 | |
| 5.1.19 | 12 / 17 | |
| 5.1.18 | 12 / 17 | |
| 5.1.17 | 12 / 17 | |
| 5.1.16 | 12 / 17 | |
| 5.1.15 | 12 / 17 | |
| 5.1.14 | 12 / 17 | |
| 5.1.13 | 12 / 17 | |
| 5.1.12 | 12 / 17 | |
| 5.1.11 | 12 / 17 | |
| 5.1.10 | 12 / 17 | |
| 5.1.9 | 12 / 17 | |
| 5.1.8 | 12 / 17 | |
| 5.1.7 | 12 / 17 | |
| 5.1.6 | 12 / 17 | |
| 5.1.0 | 12 / 17 | |
| 5.0.54 | 12 / 17 | |
| 5.0.53 | 12 / 17 | |
| 5.0.52 | 12 / 17 | |
| 5.0.51 | 12 / 17 | |
| 5.0.50 | 12 / 17 | |
| 5.0.49 | 12 / 17 | |
| 5.0.48 | 12 / 17 | |
| 5.0.47 | 12 / 17 | |
| 5.0.46 | 12 / 17 | |
| 5.0.45 | 12 / 17 | |
| 5.0.44 | 12 / 17 | |
| 5.0.43 | 12 / 17 | |
| 5.0.42 | 12 / 17 | |
| 5.0.41 | 12 / 17 | |
| 5.0.40 | 12 / 17 | |
| 5.0.39 | 12 / 17 | |
| 5.0.38 | 12 / 17 | |
| 5.0.37 | 12 / 17 | |
| 5.0.36 | 12 / 17 | |
| 5.0.35 | 12 / 17 | |
| 5.0.34 | 12 / 17 | |
| 5.0.33 | 12 / 17 | |
| 5.0.32 | 12 / 17 | |
| 5.0.31 | 12 / 17 | |
| 5.0.30 | 12 / 17 | |
| 5.0.29 | 12 / 17 | |
| 5.0.28 | 12 / 17 | |
| 5.0.27 | 12 / 17 | |
| 5.0.26 | 12 / 17 | |
| 5.0.25 | 12 / 17 | |
| 5.0.24 | 12 / 17 | |
| 5.0.23 | 12 / 17 | |
| 5.0.22 | 12 / 17 | |
| 5.0.21 | 12 / 17 | |
| 5.0.20 | 12 / 17 | |
| 5.0.19 | 12 / 17 | |
| 5.0.18 | 12 / 17 | |
| 5.0.17 | 12 / 17 | |
| 5.0.16 | 12 / 17 |
v5.1.65
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.64
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.63
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.62
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.61
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.60
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.