wait-port
Utility to wait for a TCP port to open.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): dwmkerr → dwmkerr-admin is the same author (Dave Kerr) using an admin account; 22 approved versions under this publisher with no rejections. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from dwmkerr to dwmkerr-admin is a legitimate account transition by the same developer; stable for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): dwmkerr-admin is the same author's admin account; has been sole publisher for years. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): dwmkerr replaced by dwmkerr-admin; same author consolidating to admin account. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 1.1.0 | 3 / 8 | |
| 1.0.4 | 3 / 8 | |
| 1.0.3 | 3 / 8 | |
| 1.0.1 | 3 / 8 | |
| 1.0.0 | 3 / 8 | |
| 0.3.1 | 3 / 8 | |
| 0.3.0 | 3 / 8 | |
| 0.2.14 | 3 / 9 | |
| 0.2.13 | 3 / 8 | |
| 0.2.9 | 3 / 9 | |
| 0.2.8 | 3 / 9 | |
| 0.2.7 | 3 / 9 | |
| 0.2.6 | 3 / 9 | |
| 0.2.4 | 3 / 7 | |
| 0.2.3 | 3 / 7 | |
| 0.2.2 | 3 / 6 | |
| 0.2.1 | 3 / 6 | |
| 0.2.0 | 3 / 6 | |
| 0.1.4 | 3 / 6 | |
| 0.1.3 | 2 / 5 | |
| 0.1.2 | 2 / 5 | |
| 0.1.1 | 2 / 5 |
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
3 findingsAll previous maintainers (dwmkerr) were replaced by new maintainers (dwmkerr-admin). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2022-07-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
3 findingsAll previous maintainers (dwmkerr) were replaced by new maintainers (dwmkerr-admin). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2020-05-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
3 findingsAll previous maintainers (dwmkerr) were replaced by new maintainers (dwmkerr-admin). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2020-05-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.