← Home

@whook/swagger-ui

10
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

nfroidure

Keywords

whookknifecycleRESTHTTPOpenAPIwebwrapperswagger

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:axios AI (phantom-deps): Runtime dep used by convention in this Swagger UI wrapper, not directly imported in TS source. ai
phantom-deps phantom-dep:ecstatic AI (phantom-deps): Static file server dep used at runtime by the framework, not directly imported in source. ai
phantom-deps phantom-dep:swagger-ui-dist AI (phantom-deps): Swagger UI assets served statically; referenced in config, not imported directly. ai
phantom-deps phantom-dep:@types/swagger-ui AI (phantom-deps): Type-only package loaded by convention; false positive for phantom-dep rule. ai
phantom-deps phantom-dep:ya-open-api-types AI (phantom-deps): Type-only package; phantom-dep heuristic is a stable false positive here. ai
phantom-deps phantom-dep:ya-json-schema-types AI (phantom-deps): Type-only package; phantom-dep heuristic is a stable false positive here. ai

Versions (showing 10 of 10)

Version Deps Published
25.0.0 8 / 17
24.1.1 8 / 17
24.1.0 8 / 17
24.0.1 9 / 16
24.0.0 9 / 16
23.0.0 9 / 16
22.0.0 9 / 16
21.0.1 9 / 16
21.0.0 9 / 16
20.1.2 9 / 17

v25.0.0

1 finding
LOW No provenance attestation provenance

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

v24.1.1

1 finding
LOW No provenance attestation provenance

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

v24.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.

v24.0.1

1 finding
LOW No provenance attestation provenance

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

v24.0.0

1 finding
LOW No provenance attestation provenance

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

v23.0.0

1 finding
LOW No provenance attestation provenance

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

v22.0.0

1 finding
LOW No provenance attestation provenance

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

v21.0.1

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.

v21.0.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.

v20.1.2

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.