@oclif/plugin-update
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:log-chopper | AI (phantom-deps): Known oclif dependency used for log rotation; not directly imported but legitimately declared. | ai |
Versions (showing 100 of 172)
| Version | Deps | Published |
|---|---|---|
| 4.7.56 | 10 / 28 | |
| 4.7.55 | 10 / 28 | |
| 4.7.54 | 10 / 28 | |
| 4.7.53 | 10 / 28 | |
| 4.7.52 | 10 / 28 | |
| 4.7.51 | 10 / 28 | |
| 4.7.50 | 10 / 28 | |
| 4.7.49 | 10 / 28 | |
| 4.7.48 | 10 / 28 | |
| 4.7.47 | 10 / 28 | |
| 4.7.46 | 10 / 28 | |
| 4.7.45 | 10 / 28 | |
| 4.7.44 | 10 / 28 | |
| 4.7.43 | 10 / 28 | |
| 4.7.42 | 10 / 28 | |
| 4.7.41 | 10 / 28 | |
| 4.7.40 | 10 / 28 | |
| 4.7.39 | 10 / 28 | |
| 4.7.38 | 10 / 28 | |
| 4.7.37 | 10 / 28 | |
| 4.7.36 | 10 / 28 | |
| 4.7.35 | 10 / 28 | |
| 4.7.34 | 10 / 28 | |
| 4.7.33 | 10 / 28 | |
| 4.7.32 | 10 / 28 | |
| 4.7.31 | 10 / 28 | |
| 4.7.30 | 10 / 28 | |
| 4.7.29 | 10 / 28 | |
| 4.7.28 | 10 / 28 | |
| 4.7.27 | 10 / 28 | |
| 4.7.26 | 10 / 28 | |
| 4.7.25 | 10 / 28 | |
| 4.7.24 | 10 / 28 | |
| 4.7.23 | 10 / 28 | |
| 4.7.22 | 10 / 28 | |
| 4.7.21 | 10 / 28 | |
| 4.7.20 | 10 / 28 | |
| 4.7.19 | 10 / 28 | |
| 4.7.18 | 10 / 28 | |
| 4.7.17 | 10 / 28 | |
| 4.7.16 | 10 / 28 | |
| 4.7.15 | 10 / 28 | |
| 4.7.14 | 10 / 28 | |
| 4.7.13 | 10 / 28 | |
| 4.7.12 | 10 / 28 | |
| 4.7.11 | 10 / 28 | |
| 4.7.10 | 10 / 28 | |
| 4.7.9 | 10 / 28 | |
| 4.7.8 | 10 / 28 | |
| 4.7.7 | 10 / 28 | |
| 4.7.6 | 10 / 28 | |
| 4.7.5 | 10 / 28 | |
| 4.7.4 | 10 / 28 | |
| 4.7.3 | 10 / 28 | |
| 4.7.2 | 10 / 28 | |
| 4.7.1 | 10 / 28 | |
| 4.7.0 | 10 / 28 | |
| 4.6.47 | 10 / 28 | |
| 4.6.46 | 10 / 28 | |
| 4.6.45 | 10 / 28 | |
| 4.6.44 | 10 / 28 | |
| 4.6.43 | 10 / 28 | |
| 4.6.42 | 10 / 28 | |
| 4.6.41 | 10 / 28 | |
| 4.6.40 | 10 / 28 | |
| 4.6.39 | 10 / 28 | |
| 4.6.38 | 10 / 28 | |
| 4.6.37 | 10 / 28 | |
| 4.6.36 | 10 / 28 | |
| 4.6.35 | 10 / 28 | |
| 4.6.34 | 10 / 28 | |
| 4.6.33 | 10 / 28 | |
| 4.6.32 | 10 / 28 | |
| 4.6.31 | 10 / 28 | |
| 4.6.30 | 10 / 28 | |
| 4.6.29 | 10 / 28 | |
| 4.6.28 | 10 / 28 | |
| 4.6.27 | 10 / 28 | |
| 4.6.26 | 10 / 28 | |
| 4.6.25 | 10 / 28 | |
| 4.6.24 | 10 / 28 | |
| 4.6.23 | 10 / 28 | |
| 4.6.22 | 10 / 28 | |
| 4.6.21 | 10 / 28 | |
| 4.6.20 | 10 / 28 | |
| 4.6.19 | 10 / 28 | |
| 4.6.18 | 10 / 28 | |
| 4.6.17 | 10 / 28 | |
| 4.6.16 | 10 / 28 | |
| 4.6.15 | 10 / 28 | |
| 4.6.14 | 10 / 28 | |
| 4.6.13 | 10 / 28 | |
| 4.6.12 | 10 / 28 | |
| 4.6.11 | 10 / 28 | |
| 4.6.10 | 10 / 28 | |
| 4.6.9 | 10 / 28 | |
| 4.6.8 | 10 / 28 | |
| 4.6.7 | 10 / 28 | |
| 4.6.6 | 10 / 28 | |
| 4.6.5 | 10 / 28 |
v4.7.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.