@swagger-api/apidom-ns-json-schema-draft-6 No license 21 versions

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

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.

Source	Rule	Reason	Accepted by	When
source-diff	net-exec-file:dist/apidom-ns-json-schema-draft-6.browser.min.js	AI (source-diff): Standard Vite UMD browser bundle; minified Ramda-based code, not malicious.	ai	2026/05/25
source-diff	source-size-tripled	AI (source-diff): Size increase from adding UMD browser bundle via Vite build; expected for this package.	ai	2026/05/25
phantom-deps	phantom-dep:ts-mixer	AI (phantom-deps): TypeScript utility library used in codebase; stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:@types/ramda	AI (phantom-deps): Type definitions for ramda; loaded by convention with ramda dependency.	ai	2026/04/29
phantom-deps	phantom-dep:ramda-adjunct	AI (phantom-deps): Functional programming utility; used in codebase; stable false positive.	ai	2026/04/29

Versions (showing 21 of 21)

Version	Deps	Published
1.11.2	8 / 0	2026-06-02
1.11.1	8 / 0	2026-05-12
1.11.0	8 / 0	2026-04-27
1.10.2	8 / 0	2026-04-13
1.10.1	8 / 0	2026-04-07
1.10.0	8 / 0	2026-04-01
1.9.0	8 / 0	2026-03-30
1.8.0	8 / 0	2026-03-20
1.7.0	8 / 0	2026-03-17
1.6.0	8 / 0	2026-02-27
1.5.1	8 / 0	2026-02-19
1.5.0	8 / 0	2026-02-16
1.4.0	8 / 0	2026-02-03
1.3.0	8 / 0	2026-01-23
1.2.2	8 / 0	2026-01-16
1.2.1	8 / 0	2026-01-16
1.2.0	8 / 0	2026-01-14
1.1.0	8 / 0	2025-12-19
1.0.2	8 / 0	2025-12-16
1.0.1	8 / 0	2025-12-05
1.0.0	8 / 0	2025-12-03

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