← Home

@swagger-api/apidom-ns-json-schema-draft-7

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

swagger-api

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff net-exec-file:dist/apidom-ns-json-schema-draft-7.browser.min.js AI (source-diff): Standard UMD browser bundle produced by Vite; pattern is stable for this package. ai
source-diff source-size-tripled AI (source-diff): Size increase from adding the UMD browser dist bundle; expected for this package. ai
phantom-deps phantom-dep:ts-mixer AI (phantom-deps): Monorepo build tooling dependency; stable false positive for this package. ai
phantom-deps phantom-dep:@types/ramda AI (phantom-deps): Type-only dependency loaded by convention; stable false positive. ai
phantom-deps phantom-dep:ramda-adjunct AI (phantom-deps): Used transitively via build config; stable false positive for this monorepo package. ai

Versions (showing 21 of 21)

Version Deps Published
1.11.2 8 / 0
1.11.1 8 / 0
1.11.0 8 / 0
1.10.2 8 / 0
1.10.1 8 / 0
1.10.0 8 / 0
1.9.0 8 / 0
1.8.0 8 / 0
1.7.0 8 / 0
1.6.0 8 / 0
1.5.1 8 / 0
1.5.0 8 / 0
1.4.0 8 / 0
1.3.0 8 / 0
1.2.2 8 / 0
1.2.1 8 / 0
1.2.0 8 / 0
1.1.0 8 / 0
1.0.2 8 / 0
1.0.1 8 / 0
1.0.0 8 / 0

v1.11.2

1 finding
LOW No provenance attestation provenance

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

v1.11.1

1 finding
LOW No provenance attestation provenance

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

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

2 findings
HIGH New file with network + code execution: dist/apidom-ns-json-schema-draft-7.browser.min.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v1.7.0

2 findings
HIGH New file with network + code execution: dist/apidom-ns-json-schema-draft-7.browser.min.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v1.6.0

2 findings
HIGH New file with network + code execution: dist/apidom-ns-json-schema-draft-7.browser.min.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v1.5.1

2 findings
HIGH New file with network + code execution: dist/apidom-ns-json-schema-draft-7.browser.min.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v1.5.0

1 finding
LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v1.2.2

1 finding
LOW No provenance attestation provenance

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

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. 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. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.2

1 finding
LOW No provenance attestation provenance

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

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

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