@gjsify/process
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib/esm/streams.js | AI (source-diff): Minified ESM bundle output from rollup/esbuild build pipeline; content is readable GJS stream polyfill logic, not obfuscated malware. | ai | |
| phantom-deps | phantom-dep:@gjsify/utils | AI (phantom-deps): Same-org dep used transitively via bundled output; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@gjsify/string_decoder | AI (phantom-deps): Same-org dep imported in bundled output (streams.js); phantom-dep heuristic fires on bundled packages. | ai | |
| phantom-deps | phantom-dep:@gjsify/terminal-native | AI (phantom-deps): Same-org dep imported in bundled output; stable false positive for this package. | ai | |
| semgrep | semgrep:env-bulk-read | AI (semgrep): Fires only in test spec files verifying env enumeration behavior; not production code. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 0.13.0 | 4 / 4 | |
| 0.4.25 | 3 / 4 | |
| 0.4.5 | 3 / 4 | |
| 0.4.4 | 3 / 4 | |
| 0.4.3 | 3 / 4 | |
| 0.4.0 | 3 / 4 | |
| 0.3.21 | 3 / 4 | |
| 0.3.20 | 3 / 4 | |
| 0.3.19 | 3 / 4 | |
| 0.3.18 | 3 / 4 | |
| 0.3.17 | 3 / 4 | |
| 0.3.16 | 3 / 4 | |
| 0.3.15 | 3 / 4 | |
| 0.3.14 | 3 / 4 | |
| 0.3.13 | 3 / 4 | |
| 0.3.12 | 3 / 4 | |
| 0.3.11 | 3 / 4 | |
| 0.3.10 | 3 / 4 | |
| 0.3.9 | 3 / 4 | |
| 0.3.8 | 3 / 4 | |
| 0.3.7 | 3 / 4 | |
| 0.3.6 | 3 / 4 | |
| 0.3.5 | 3 / 4 | |
| 0.3.4 | 3 / 4 | |
| 0.3.3 | 3 / 4 | |
| 0.3.2 | 3 / 4 | |
| 0.3.1 | 3 / 4 | |
| 0.3.0 | 3 / 4 | |
| 0.2.0 | 2 / 4 | |
| 0.1.15 | 1 / 4 | |
| 0.1.13 | 1 / 4 | |
| 0.1.12 | 1 / 4 | |
| 0.1.11 | 1 / 4 | |
| 0.1.10 | 1 / 4 | |
| 0.1.9 | 1 / 4 | |
| 0.1.8 | 1 / 4 | |
| 0.1.7 | 1 / 4 | |
| 0.1.6 | 1 / 4 | |
| 0.1.5 | 1 / 4 | |
| 0.1.4 | 1 / 4 | |
| 0.1.3 | 1 / 4 | |
| 0.1.2 | 1 / 4 | |
| 0.1.1 | 1 / 4 | |
| 0.1.0 | 1 / 4 |
v0.13.0
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-06-27. 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.