@types/detect-port MIT 8 versions

@types/detect-port

npm

Stub TypeScript definitions entry for detect-port, which provides its own types definitions

8

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

types

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	dormant-publish	AI (publish-pattern): Dormancy followed by a deprecation stub publish is expected for @types packages when upstream ships its own types. Trusted `types` publisher with 10k+ approvals.	ai	2026/04/23
publish-pattern	new-deps-added	AI (publish-pattern): The detect-port dependency is the intentional redirect for this stub deprecation package — not an attack vector.	ai	2026/04/23
bogus-package	bogus-package	AI (bogus-package): Stub/deprecation @types packages legitimately have no code, no README instructions, and minimal metadata. This is the standard pattern.	ai	2026/04/23
phantom-deps	phantom-dep:detect-port	AI (phantom-deps): Stub package; detect-port is a redirect dependency, not imported in code. Expected for this package type.	ai	2026/04/23

Versions (showing 8 of 8)

Version	Deps	Published
2.0.0	1 / 0	2025-04-04
1.3.5	0 / 0	2023-11-07
1.3.4	0 / 0	2023-10-18
1.3.3	0 / 0	2023-05-28
1.3.2	0 / 0	2021-12-23
1.3.1	0 / 0	2021-07-06
1.3.0	0 / 0	2020-05-03
1.1.0	0 / 0	2017-03-29

v2.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.