@teambit/toolbox.network.get-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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.0.24 | 0 / 4 | |
| 1.0.23 | 0 / 4 | |
| 1.0.22 | 0 / 4 | |
| 1.0.21 | 0 / 4 | |
| 1.0.20 | 0 / 4 | |
| 1.0.19 | 0 / 4 | |
| 1.0.18 | 0 / 4 | |
| 1.0.17 | 0 / 4 | |
| 1.0.16 | 0 / 4 | |
| 1.0.15 | 0 / 4 | |
| 1.0.14 | 0 / 4 | |
| 1.0.13 | 0 / 4 | |
| 1.0.12 | 0 / 4 | |
| 1.0.11 | 0 / 4 | |
| 1.0.10 | 0 / 4 | |
| 1.0.9 | 0 / 4 | |
| 1.0.8 | 0 / 5 | |
| 1.0.7 | 0 / 6 |
v1.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.