@gjsify/worker_threads
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): gjsify org uses GitHub Actions CI for publishing; consistent with automated release pipeline. | ai | |
| source-diff | obfuscated-file:lib/esm/browser.js | AI (source-diff): Minified browser bundle output; readable logic visible in sample, no obfuscation or payload. | ai | |
| source-diff | obfuscated-file:lib/types/worker-bootstrap.d.ts | AI (source-diff): Long line is an inlined source string constant in a .d.ts file, not obfuscated code. | ai | |
| phantom-deps | phantom-dep:@girs/glib-2.0 | AI (phantom-deps): GJS type-binding package; referenced in config/types only, not directly imported at runtime — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@girs/gio-2.0 | AI (phantom-deps): GJS type-binding package; referenced in config/types only, not directly imported at runtime — stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@girs/glib-2.0 | AI (dependencies): GObject introspection binding; expected runtime dep for a GJS compatibility package. | ai | |
| dependencies | unvetted-dep:@girs/gio-2.0 | AI (dependencies): GObject introspection binding; expected runtime dep for a GJS compatibility package. | ai | |
| phantom-deps | phantom-dep:@gjsify/events | AI (phantom-deps): Same-org dependency; may be re-exported or used indirectly via type-only imports in a library package. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.4.38 | 5 / 5 | |
| 0.4.27 | 5 / 5 | |
| 0.4.26 | 5 / 5 | |
| 0.4.13 | 4 / 5 | |
| 0.4.10 | 3 / 5 | |
| 0.4.0 | 3 / 5 | |
| 0.3.21 | 3 / 5 | |
| 0.3.20 | 3 / 5 | |
| 0.3.19 | 3 / 5 | |
| 0.3.18 | 3 / 5 | |
| 0.3.17 | 3 / 5 | |
| 0.3.12 | 3 / 5 | |
| 0.3.11 | 3 / 5 | |
| 0.3.9 | 3 / 5 | |
| 0.1.8 | 3 / 5 | |
| 0.1.5 | 3 / 5 | |
| 0.1.4 | 3 / 5 | |
| 0.1.3 | 3 / 5 | |
| 0.1.2 | 3 / 5 | |
| 0.1.0 | 3 / 5 |
v0.4.38
4 findingsThis version was published by a different npm account than previous versions on 2026-06-05. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.27
3 findingsThis version was published by a different npm account than previous versions on 2026-05-26. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.26
3 findingsThis version was published by a different npm account than previous versions on 2026-05-26. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.