get-port
Get an available port
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 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 7.2.0 | 0 / 4 | |
| 7.1.0 | 0 / 4 | |
| 7.0.0 | 0 / 4 | |
| 6.1.2 | 0 / 5 | |
| 6.1.1 | 0 / 5 | |
| 6.1.0 | 0 / 5 | |
| 6.0.0 | 0 / 5 | |
| 5.1.1 | 0 / 4 | |
| 5.1.0 | 0 / 4 | |
| 5.0.0 | 1 / 4 | |
| 4.2.0 | 0 / 4 | |
| 4.1.0 | 0 / 3 | |
| 4.0.0 | 0 / 3 | |
| 3.2.0 | 0 / 3 | |
| 3.1.0 | 0 / 2 | |
| 3.0.0 | 0 / 2 | |
| 2.1.0 | 1 / 2 | |
| 2.0.0 | 1 / 2 | |
| 1.0.0 | 0 / 1 | |
| 0.1.0 | 0 / 1 |
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.