@kevisual/cli
envision 命令行工具
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 | net-exec-file:dist/assistant-opencode.js | AI (source-diff): Bundled network+exec code from opencode SDK client, dual-use not malicious. | ai | |
| source-diff | obfuscated-file:dist/assistant-opencode.js | AI (source-diff): Bundled esbuild/bun output for new SDK integration, not obfuscation. | ai | |
| phantom-deps | phantom-dep:@nut-tree-fork/nut-js | AI (phantom-deps): Referenced in config files, not directly imported but used. | ai | |
| phantom-deps | phantom-dep:@kevisual/hot-api | AI (phantom-deps): Config-file reference, same org scope. | ai | |
| phantom-deps | phantom-dep:@kevisual/context | AI (phantom-deps): Config-file reference, same org scope. | ai | |
| dependencies | unvetted-dep:@kevisual/hot-api | AI (dependencies): Same-org first-party package, not a hostile dependency. | ai | |
| phantom-deps | phantom-dep:eventemitter3 | AI (phantom-deps): Bundled CLI; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:@kevisual/auth | AI (phantom-deps): Same-org scoped dep; bundled output pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:@opencode-ai/sdk | AI (phantom-deps): Bundled CLI; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:@inquirer/prompts | AI (phantom-deps): Bundled CLI; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:dayjs | AI (phantom-deps): Declared runtime dep; bundled via bun, not directly imported in analyzed files. | ai | |
| phantom-deps | phantom-dep:lowdb | AI (phantom-deps): Declared runtime dep; bundled via bun, not directly imported in analyzed files. | ai | |
| phantom-deps | phantom-dep:react | AI (phantom-deps): Declared runtime dep (used with ink); bundled via bun. | ai | |
| phantom-deps | phantom-dep:busboy | AI (phantom-deps): Declared runtime dep; bundled via bun, not directly imported in analyzed files. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): Declared runtime dep; bundled via bun, not directly imported in analyzed files. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): Declared runtime dep; bundled via bun, not directly imported in analyzed files. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): Declared runtime dep; bundled via bun, not directly imported in analyzed files. | ai | |
| phantom-deps | phantom-dep:hash-wasm | AI (phantom-deps): Declared runtime dep; bundled via bun. | ai | |
| phantom-deps | phantom-dep:lru-cache | AI (phantom-deps): Declared runtime dep; bundled via bun, not directly imported in analyzed files. | ai | |
| phantom-deps | phantom-dep:unstorage | AI (phantom-deps): Declared runtime dep; bundled via bun, not directly imported in analyzed files. | ai | |
| phantom-deps | phantom-dep:micromatch | AI (phantom-deps): Declared runtime dep; bundled via bun, not directly imported in analyzed files. | ai | |
| phantom-deps | phantom-dep:gray-matter | AI (phantom-deps): Declared runtime dep; bundled via bun, not directly imported in analyzed files. | ai | |
| phantom-deps | phantom-dep:@kevisual/app | AI (phantom-deps): Same-org dep; bundled via bun. | ai | |
| phantom-deps | phantom-dep:@types/busboy | AI (phantom-deps): Type-only dep; false positive for phantom-dep rule. | ai | |
| phantom-deps | phantom-dep:yaml | AI (phantom-deps): Declared runtime dep; bundled via bun, not directly imported in analyzed files. | ai | |
| phantom-deps | phantom-dep:jose | AI (phantom-deps): Declared runtime dep; bundled via bun, not directly imported in analyzed files. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Declared runtime dep; bundled via bun, not directly imported in analyzed files. | ai | |
| phantom-deps | phantom-dep:pm2 | AI (phantom-deps): Declared runtime dep; bundled via bun, not directly imported in analyzed files. | ai | |
| phantom-deps | phantom-dep:ink | AI (phantom-deps): Declared runtime dep; bundled via bun, not directly imported in analyzed files. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @kevisual/cli; levenshtein match to 'joi' is a false positive across all versions. | ai |
Versions (showing 51 of 67)
| Version | Deps | Published |
|---|---|---|
| 0.1.45 | 27 / 25 | |
| 0.1.44 | 27 / 25 | |
| 0.1.43 | 27 / 25 | |
| 0.1.41 | 27 / 25 | |
| 0.1.40 | 23 / 24 | |
| 0.1.39 | 23 / 24 | |
| 0.1.38 | 23 / 24 | |
| 0.1.37 | 22 / 25 | |
| 0.1.36 | 22 / 25 | |
| 0.1.32 | 18 / 23 | |
| 0.1.31 | 18 / 23 | |
| 0.1.30 | 18 / 23 | |
| 0.1.29 | 18 / 23 | |
| 0.1.28 | 18 / 23 | |
| 0.1.27 | 18 / 23 | |
| 0.1.26 | 18 / 23 | |
| 0.1.25 | 18 / 23 | |
| 0.1.24 | 18 / 23 | |
| 0.1.23 | 18 / 23 | |
| 0.1.22 | 18 / 23 | |
| 0.1.21 | 18 / 23 | |
| 0.1.20 | 18 / 23 | |
| 0.1.19 | 18 / 23 | |
| 0.1.18 | 17 / 23 | |
| 0.1.17 | 16 / 23 | |
| 0.1.16 | 16 / 23 | |
| 0.1.15 | 16 / 23 | |
| 0.1.14 | 16 / 23 | |
| 0.1.13 | 16 / 23 | |
| 0.1.12 | 16 / 23 | |
| 0.1.11 | 16 / 23 | |
| 0.1.10 | 16 / 23 | |
| 0.1.9 | 16 / 23 | |
| 0.1.8 | 16 / 23 | |
| 0.1.7 | 16 / 23 | |
| 0.1.6 | 16 / 23 | |
| 0.1.5 | 16 / 24 | |
| 0.1.4 | 16 / 24 | |
| 0.1.3 | 16 / 24 | |
| 0.1.2 | 16 / 23 | |
| 0.1.1 | 16 / 23 | |
| 0.1.0 | 16 / 23 | |
| 0.0.99 | 16 / 22 | |
| 0.0.98 | 16 / 22 | |
| 0.0.97 | 16 / 22 | |
| 0.0.96 | 16 / 22 | |
| 0.0.95 | 16 / 22 | |
| 0.0.94 | 16 / 22 | |
| 0.0.93 | 16 / 22 | |
| 0.0.92 | 14 / 22 | |
| 0.0.91 | 14 / 22 |
v0.1.32
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.31
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.99
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.98
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.97
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.96
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.95
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.94
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.93
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.92
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.91
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.