@xwiki/cristal-sharedworker-impl LGPL 2.1 7 versions

@xwiki/cristal-sharedworker-impl

npm Repository Homepage

7

Versions

LGPL 2.1

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

xwikiorgnpmtmortagneesurlimanuelleducpierre.jeanjeanmarius.dumitru.floreavmassolmichael.hamann

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	net-exec-file:dist/assets/worker-jC4O7JRI.js	AI (source-diff): Vite-bundled SharedWorker output; reflect-metadata + comlink bundle pattern, not malware.	ai	2026/05/08
source-diff	net-exec-file:dist/assets/worker-eCtrZdjN.js	AI (source-diff): Vite-bundled SharedWorker output; network calls and eval-like patterns are from reflect-metadata/comlink polyfills, not malware.	ai	2026/05/08
source-diff	net-exec-file:dist/assets/worker-D7QAxgKq.js	AI (source-diff): Vite-bundled SharedWorker; eval usage is reflect-metadata's global-object polyfill, not malicious code execution.	ai	2026/05/08
dependencies	unvetted-dep:@xwiki/cristal-api	AI (dependencies): Same XWiki/cristal monorepo sibling package, pinned to matching version.	ai	2026/05/08
dependencies	unvetted-dep:@xwiki/cristal-document-api	AI (dependencies): Same XWiki/cristal monorepo sibling package, pinned to matching version.	ai	2026/05/08
dependencies	unvetted-dep:@xwiki/cristal-configuration-api	AI (dependencies): Same XWiki/cristal monorepo sibling package, pinned to matching version.	ai	2026/05/08

Versions (showing 7 of 7)

Version	Deps	Published
1.4.0	14 / 7	2026-05-28
1.3.0	14 / 7	2026-04-30
1.2.0	14 / 7	2026-03-31
1.1.0	14 / 7	2026-02-24
1.0.0	14 / 7	2026-01-27
0.25.0	14 / 7	2025-12-22
0.24.0	14 / 7	2025-11-24

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.0

2 findings

HIGH New file with network + code execution: dist/assets/worker-jC4O7JRI.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.1.0

2 findings

HIGH New file with network + code execution: dist/assets/worker-D7QAxgKq.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.0.0

2 findings

HIGH New file with network + code execution: dist/assets/worker-eCtrZdjN.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.

v0.25.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.

v0.24.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.