@live-change/scope-service
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Versions (showing 47 of 147)
| Version | Deps | Published |
|---|---|---|
| 0.9.108 | 3 / 0 | |
| 0.9.107 | 3 / 0 | |
| 0.9.106 | 3 / 0 | |
| 0.9.105 | 3 / 0 | |
| 0.9.104 | 3 / 0 | |
| 0.9.103 | 3 / 0 | |
| 0.9.102 | 3 / 0 | |
| 0.9.101 | 3 / 0 | |
| 0.9.100 | 3 / 0 | |
| 0.9.99 | 3 / 0 | |
| 0.9.98 | 3 / 0 | |
| 0.9.97 | 3 / 0 | |
| 0.9.96 | 3 / 0 | |
| 0.9.95 | 3 / 0 | |
| 0.9.94 | 3 / 0 | |
| 0.9.93 | 3 / 0 | |
| 0.9.92 | 3 / 0 | |
| 0.9.91 | 3 / 0 | |
| 0.9.90 | 3 / 0 | |
| 0.9.89 | 3 / 0 | |
| 0.9.88 | 3 / 0 | |
| 0.9.87 | 3 / 0 | |
| 0.9.86 | 3 / 0 | |
| 0.9.85 | 3 / 0 | |
| 0.9.84 | 3 / 0 | |
| 0.9.83 | 3 / 0 | |
| 0.9.82 | 3 / 0 | |
| 0.9.81 | 3 / 0 | |
| 0.9.80 | 3 / 0 | |
| 0.9.79 | 3 / 0 | |
| 0.9.78 | 3 / 0 | |
| 0.9.77 | 3 / 0 | |
| 0.9.76 | 3 / 0 | |
| 0.9.75 | 3 / 0 | |
| 0.9.74 | 3 / 0 | |
| 0.9.73 | 3 / 0 | |
| 0.9.72 | 3 / 0 | |
| 0.9.71 | 3 / 0 | |
| 0.9.70 | 3 / 0 | |
| 0.9.69 | 3 / 0 | |
| 0.9.68 | 3 / 0 | |
| 0.9.67 | 3 / 0 | |
| 0.9.66 | 3 / 0 | |
| 0.9.65 | 3 / 0 | |
| 0.9.64 | 3 / 0 | |
| 0.9.63 | 3 / 0 | |
| 0.9.62 | 3 / 0 |
v0.9.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.