@live-change/task-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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Internal monorepo service package; missing description is a consistent pattern across this publisher's packages. | ai | |
| provenance | no-provenance | AI (provenance): Publisher consistently publishes without provenance; stable pattern across 326 versions. | ai |
Versions (showing 51 of 336)
| Version | Deps | Published |
|---|---|---|
| 0.9.216 | 2 / 0 | |
| 0.9.215 | 2 / 0 | |
| 0.9.214 | 2 / 0 | |
| 0.9.213 | 2 / 0 | |
| 0.9.212 | 2 / 0 | |
| 0.9.209 | 2 / 0 | |
| 0.9.208 | 2 / 0 | |
| 0.9.207 | 2 / 0 | |
| 0.9.206 | 2 / 0 | |
| 0.9.205 | 2 / 0 | |
| 0.9.204 | 2 / 0 | |
| 0.9.203 | 2 / 0 | |
| 0.9.201 | 2 / 0 | |
| 0.9.200 | 2 / 0 | |
| 0.9.199 | 2 / 0 | |
| 0.9.198 | 2 / 0 | |
| 0.9.197 | 2 / 0 | |
| 0.9.196 | 2 / 0 | |
| 0.9.195 | 2 / 0 | |
| 0.9.194 | 2 / 0 | |
| 0.9.193 | 2 / 0 | |
| 0.9.192 | 2 / 0 | |
| 0.9.191 | 2 / 0 | |
| 0.9.190 | 2 / 0 | |
| 0.9.189 | 2 / 0 | |
| 0.9.188 | 2 / 0 | |
| 0.9.187 | 2 / 0 | |
| 0.9.186 | 2 / 0 | |
| 0.9.185 | 2 / 0 | |
| 0.9.184 | 2 / 0 | |
| 0.9.183 | 2 / 0 | |
| 0.9.182 | 2 / 0 | |
| 0.9.181 | 2 / 0 | |
| 0.9.180 | 2 / 0 | |
| 0.9.179 | 2 / 0 | |
| 0.9.177 | 2 / 0 | |
| 0.9.176 | 2 / 0 | |
| 0.9.175 | 2 / 0 | |
| 0.9.174 | 2 / 0 | |
| 0.9.173 | 2 / 0 | |
| 0.9.171 | 2 / 0 | |
| 0.9.169 | 2 / 0 | |
| 0.9.167 | 2 / 0 | |
| 0.9.166 | 2 / 0 | |
| 0.9.165 | 2 / 0 | |
| 0.9.164 | 2 / 0 | |
| 0.9.163 | 2 / 0 | |
| 0.9.162 | 2 / 0 | |
| 0.9.161 | 2 / 0 | |
| 0.9.160 | 2 / 0 | |
| 0.9.159 | 2 / 0 |
v0.9.216
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.215
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.214
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.213
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.212
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.203
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.201
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.199
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.198
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.193
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.192
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.190
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.187
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.186
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.185
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.183
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.182
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.181
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.180
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.176
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.175
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.174
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.173
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.171
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.169
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.167
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.166
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.164
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.163
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.162
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.161
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.160
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.159
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.