← Home

@targetprocess/swagger-tools

npm Repository Homepage
7
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

targetprocess-user

Keywords

apiconnectmiddlewareswagger

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:new-function-constructor AI (semgrep): Inside webpack-bundled swagger-ui asset; standard bundler output, not malicious code. ai
semgrep semgrep:dynamic-require AI (semgrep): Controller-loader pattern in swagger-router; resolves paths from a configured directory, not arbitrary user input. ai
phantom-deps phantom-dep:commander AI (phantom-deps): commander is declared in dependencies and used in bin/swagger-tools CLI; stable false positive. ai
phantom-deps phantom-dep:superagent AI (phantom-deps): superagent is declared in dependencies; phantom-dep heuristic misses indirect/conditional imports. ai

Versions (showing 7 of 7)

Version Deps Published
1.2.1 17 / 24
1.2.0 17 / 24
1.1.3 17 / 24
1.1.2 17 / 24
1.1.1 17 / 24
1.1.0 17 / 24
1.0.2 17 / 24

v1.2.1

1 finding
LOW No provenance attestation provenance

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

v1.2.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.

v1.1.3

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.

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

v1.1.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.

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.

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