@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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Versions (showing 51 of 56)
| Version | Deps | Published |
|---|---|---|
| 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 |
v4.7.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.