@live-change/image-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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Part of a large monorepo; sparse metadata is consistent across all 416 versions of this ecosystem. | ai | |
| phantom-deps | phantom-dep:pluralize | AI (phantom-deps): pluralize is a declared runtime dep; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 100 of 339)
| Version | Deps | Published |
|---|---|---|
| 0.9.109 | 5 / 0 | |
| 0.9.108 | 5 / 0 | |
| 0.9.107 | 5 / 0 | |
| 0.9.106 | 5 / 0 | |
| 0.9.105 | 5 / 0 | |
| 0.9.104 | 5 / 0 | |
| 0.9.103 | 5 / 0 | |
| 0.9.102 | 5 / 0 | |
| 0.9.101 | 5 / 0 | |
| 0.9.100 | 5 / 0 | |
| 0.9.99 | 5 / 0 | |
| 0.9.98 | 5 / 0 | |
| 0.9.97 | 5 / 0 | |
| 0.9.96 | 5 / 0 | |
| 0.9.95 | 5 / 0 | |
| 0.9.94 | 5 / 0 | |
| 0.9.93 | 5 / 0 | |
| 0.9.92 | 5 / 0 | |
| 0.9.91 | 5 / 0 | |
| 0.9.90 | 5 / 0 | |
| 0.9.89 | 5 / 0 | |
| 0.9.88 | 5 / 0 | |
| 0.9.87 | 5 / 0 | |
| 0.9.86 | 5 / 0 | |
| 0.9.85 | 5 / 0 | |
| 0.9.84 | 5 / 0 | |
| 0.9.83 | 5 / 0 | |
| 0.9.82 | 5 / 0 | |
| 0.9.81 | 5 / 0 | |
| 0.9.80 | 5 / 0 | |
| 0.9.79 | 5 / 0 | |
| 0.9.78 | 5 / 0 | |
| 0.9.77 | 5 / 0 | |
| 0.9.76 | 5 / 0 | |
| 0.9.75 | 5 / 0 | |
| 0.9.74 | 5 / 0 | |
| 0.9.73 | 5 / 0 | |
| 0.9.72 | 5 / 0 | |
| 0.9.71 | 5 / 0 | |
| 0.9.70 | 5 / 0 | |
| 0.9.69 | 5 / 0 | |
| 0.9.68 | 5 / 0 | |
| 0.9.67 | 5 / 0 | |
| 0.9.66 | 5 / 0 | |
| 0.9.65 | 5 / 0 | |
| 0.9.64 | 5 / 0 | |
| 0.9.63 | 5 / 0 | |
| 0.9.62 | 5 / 0 | |
| 0.9.61 | 5 / 0 | |
| 0.9.60 | 5 / 0 | |
| 0.9.59 | 5 / 0 | |
| 0.9.58 | 5 / 0 | |
| 0.9.57 | 5 / 0 | |
| 0.9.56 | 5 / 0 | |
| 0.9.55 | 5 / 0 | |
| 0.9.54 | 5 / 0 | |
| 0.9.53 | 5 / 0 | |
| 0.9.52 | 5 / 0 | |
| 0.9.51 | 5 / 0 | |
| 0.9.50 | 5 / 0 | |
| 0.9.49 | 5 / 0 | |
| 0.9.48 | 5 / 0 | |
| 0.9.47 | 5 / 0 | |
| 0.9.46 | 5 / 0 | |
| 0.9.45 | 5 / 0 | |
| 0.9.44 | 5 / 0 | |
| 0.9.43 | 5 / 0 | |
| 0.9.42 | 5 / 0 | |
| 0.9.41 | 5 / 0 | |
| 0.9.40 | 5 / 0 | |
| 0.9.39 | 5 / 0 | |
| 0.9.38 | 5 / 0 | |
| 0.9.37 | 5 / 0 | |
| 0.9.36 | 5 / 0 | |
| 0.9.35 | 5 / 0 | |
| 0.9.34 | 5 / 0 | |
| 0.9.33 | 5 / 0 | |
| 0.9.32 | 5 / 0 | |
| 0.9.31 | 5 / 0 | |
| 0.9.30 | 5 / 0 | |
| 0.9.29 | 5 / 0 | |
| 0.9.28 | 5 / 0 | |
| 0.9.27 | 5 / 0 | |
| 0.9.26 | 5 / 0 | |
| 0.9.25 | 5 / 0 | |
| 0.9.24 | 5 / 0 | |
| 0.9.23 | 5 / 0 | |
| 0.9.22 | 5 / 0 | |
| 0.9.21 | 5 / 0 | |
| 0.9.20 | 5 / 0 | |
| 0.9.19 | 5 / 0 | |
| 0.9.18 | 5 / 0 | |
| 0.9.17 | 5 / 0 | |
| 0.9.16 | 5 / 0 | |
| 0.9.15 | 5 / 0 | |
| 0.9.14 | 5 / 0 | |
| 0.9.13 | 5 / 0 | |
| 0.9.12 | 5 / 0 | |
| 0.9.11 | 5 / 0 | |
| 0.9.10 | 5 / 0 |
v0.9.108
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
v0.9.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.