windows-release
Get the name of a Windows version from the release number: `5.1.2600` → `XP`
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 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 7.1.1 | 1 / 2 | |
| 7.1.0 | 1 / 2 | |
| 7.0.0 | 0 / 2 | |
| 6.1.0 | 1 / 3 | |
| 6.0.1 | 1 / 3 | |
| 6.0.0 | 1 / 3 | |
| 5.1.1 | 1 / 3 | |
| 5.1.0 | 1 / 3 | |
| 5.0.1 | 1 / 3 | |
| 5.0.0 | 1 / 3 | |
| 4.0.0 | 1 / 3 | |
| 3.3.3 | 1 / 3 | |
| 3.3.2 | 1 / 3 | |
| 3.3.1 | 1 / 3 | |
| 3.3.0 | 1 / 3 | |
| 3.2.0 | 1 / 3 | |
| 3.1.0 | 1 / 2 |
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.