@work.books/cli
Build tool for workbooks — compiles a multi-file source tree into a single, self-contained .workbook.html.
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:src/util/authCallbackPage.mjs | AI (source-diff): Long line is a template-literal HTML page, not obfuscated code. | ai | |
| source-diff | obfuscated-file:src/encrypt/wrapStudio.mjs | AI (source-diff): Readable, commented encryption code; long lines are base64/crypto helpers not obfuscation. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 127.0.0.1 is the loopback OAuth callback listener — not an external raw IP. | ai | |
| semgrep | semgrep:shady-links-tlds | AI (semgrep): URL appears only in a code comment as a usage example, not in live code. | ai | |
| semgrep | semgrep:silent-process-exec | AI (semgrep): Spawns system browser (xdg-open/open/start) to open OAuth URL — standard browser-launch pattern, not a reverse shell. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @work.books/cli is not plausibly a typosquat of joi; edit-distance match is coincidental. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes embedded bundle data from HTML files — documented feature of the tool, not payload obfuscation. | ai | |
| semgrep | semgrep:silent-process-exec-var | AI (semgrep): Same browser-launch pattern as silent-process-exec; stable false positive for this package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.9.2 | 11 / 0 | |
| 0.9.1 | 11 / 0 | |
| 0.9.0 | 11 / 0 | |
| 0.8.1 | 11 / 0 | |
| 0.8.0 | 9 / 0 | |
| 0.7.2 | 9 / 0 | |
| 0.7.1 | 9 / 0 | |
| 0.7.0 | 9 / 0 | |
| 0.6.0 | 9 / 0 | |
| 0.5.4 | 7 / 0 | |
| 0.5.3 | 7 / 0 | |
| 0.5.2 | 7 / 0 | |
| 0.5.1 | 7 / 0 | |
| 0.3.0 | 6 / 0 | |
| 0.2.3 | 3 / 0 | |
| 0.2.2 | 3 / 0 | |
| 0.2.1 | 2 / 0 | |
| 0.2.0 | 2 / 0 | |
| 0.1.0 | 2 / 0 |
v0.9.2
2 findingsNewly 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.9.1
2 findingsNewly 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.9.0
2 findingsNewly 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.8.1
2 findingsNewly 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.8.0
2 findingsNewly 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.7.2
2 findingsNewly 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.7.1
2 findingsNewly 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.7.0
2 findingsNewly 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.5.1
2 findingsNewly 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.