@polka-codes/cli
[](https://www.npmjs.com/package/@polka-codes/cli) [](https://www.npmjs.com/package/@polka-codes/cli) [: Config-referenced AI provider; stable pattern for this CLI package. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from personal account to GitHub Actions CI publisher with SLSA provenance; legitimate automation migration. | ai | |
| source-diff | net-exec-file:dist/bin.cjs | AI (source-diff): CLI tool legitimately makes network calls (AI SDK) and uses dynamic requires via bundler shims; not dropper behavior. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase reflects bundling all deps into a single CJS binary via tsup; expected for a CLI tool. | ai | |
| source-diff | obfuscated-file:dist/bin.cjs | AI (source-diff): dist/bin.cjs is a tsup-bundled CLI binary; long lines are standard bundler output, not obfuscation. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Config-file reference pattern; stable for this CLI package. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): Config-referenced environment loader; stable pattern for this CLI package. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): Config-referenced CLI framework; stable pattern for this CLI package. | ai | |
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): Config-referenced utility library; stable pattern for this CLI package. | ai | |
| phantom-deps | phantom-dep:mime-types | AI (phantom-deps): Config-referenced MIME utility; stable pattern for this CLI package. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/google | AI (phantom-deps): Config-referenced AI provider; stable pattern for this CLI package. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/deepseek | AI (phantom-deps): Config-referenced AI provider; stable pattern for this CLI package. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/provider | AI (phantom-deps): Config-referenced AI provider base; stable pattern for this CLI package. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/anthropic | AI (phantom-deps): Config-referenced AI provider; stable pattern for this CLI package. | ai | |
| phantom-deps | phantom-dep:@inquirer/prompts | AI (phantom-deps): Config-referenced CLI prompts; stable pattern for this CLI package. | ai | |
| phantom-deps | phantom-dep:@polka-codes/core | AI (phantom-deps): Same-org scoped dependency; stable pattern for this CLI package. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/google-vertex | AI (phantom-deps): Config-referenced AI provider; stable pattern for this CLI package. | ai | |
| phantom-deps | phantom-dep:ollama-ai-provider-v2 | AI (phantom-deps): Config-referenced AI provider; stable pattern for this CLI package. | ai | |
| phantom-deps | phantom-dep:@polka-codes/cli-shared | AI (phantom-deps): Same-org scoped dependency; stable pattern for this CLI package. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/openai-compatible | AI (phantom-deps): Config-referenced AI provider; stable pattern for this CLI package. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/openai | AI (phantom-deps): Config-referenced AI provider; stable pattern for this CLI package. | ai | |
| phantom-deps | phantom-dep:ai | AI (phantom-deps): Config-referenced AI SDK dependency; stable pattern for this CLI package. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Config-referenced validation library; stable pattern for this CLI package. | ai | |
| phantom-deps | phantom-dep:ulid | AI (phantom-deps): Config-referenced utility; stable pattern for this CLI package. | ai | |
| phantom-deps | phantom-dep:yaml | AI (phantom-deps): Config-referenced parser; stable pattern for this CLI package. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): Config-referenced CLI styling; stable pattern for this CLI package. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @polka-codes/cli is not a plausible typosquat of joi; different namespace and purpose. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/provider-utils | AI (phantom-deps): Declared runtime dep; used transitively or indirectly in bundled CLI output. | ai | |
| phantom-deps | phantom-dep:ora | AI (phantom-deps): ora is a declared runtime dep in package.json; phantom-dep heuristic false positive for this CLI bundle. | ai |
Versions (showing 51 of 145)
| Version | Deps | Published |
|---|---|---|
| 0.10.32 | 23 / 2 | |
| 0.10.31 | 23 / 2 | |
| 0.10.30 | 23 / 2 | |
| 0.10.29 | 23 / 2 | |
| 0.10.28 | 23 / 2 | |
| 0.10.27 | 23 / 2 | |
| 0.10.26 | 23 / 2 | |
| 0.10.25 | 23 / 2 | |
| 0.10.24 | 23 / 2 | |
| 0.10.23 | 23 / 2 | |
| 0.10.22 | 23 / 2 | |
| 0.10.21 | 23 / 2 | |
| 0.10.20 | 23 / 2 | |
| 0.10.19 | 23 / 2 | |
| 0.10.18 | 23 / 2 | |
| 0.10.17 | 23 / 2 | |
| 0.10.16 | 23 / 2 | |
| 0.10.13 | 23 / 2 | |
| 0.10.11 | 23 / 2 | |
| 0.10.10 | 23 / 2 | |
| 0.10.9 | 23 / 2 | |
| 0.10.8 | 23 / 2 | |
| 0.10.6 | 23 / 2 | |
| 0.10.5 | 23 / 2 | |
| 0.10.3 | 23 / 2 | |
| 0.10.1 | 23 / 2 | |
| 0.9.102 | 24 / 2 | |
| 0.9.101 | 24 / 2 | |
| 0.9.100 | 24 / 2 | |
| 0.9.99 | 24 / 2 | |
| 0.9.98 | 24 / 2 | |
| 0.9.97 | 24 / 2 | |
| 0.9.96 | 24 / 2 | |
| 0.9.95 | 24 / 2 | |
| 0.9.94 | 24 / 2 | |
| 0.9.93 | 24 / 2 | |
| 0.9.92 | 24 / 2 | |
| 0.9.91 | 24 / 2 | |
| 0.9.90 | 24 / 2 | |
| 0.9.89 | 24 / 2 | |
| 0.9.88 | 24 / 2 | |
| 0.9.86 | 23 / 2 | |
| 0.9.85 | 23 / 2 | |
| 0.9.84 | 22 / 2 | |
| 0.9.83 | 22 / 2 | |
| 0.9.82 | 22 / 2 | |
| 0.9.81 | 21 / 2 | |
| 0.9.80 | 21 / 2 | |
| 0.9.79 | 21 / 2 | |
| 0.9.78 | 21 / 2 | |
| 0.9.77 | 21 / 2 |
v0.10.32
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.31
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.30
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.26
4 findingsThis version was published by a different npm account than previous versions on 2026-04-10. 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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.25
4 findingsThis version was published by a different npm account than previous versions on 2026-04-07. 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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.24
2 findingsThis version was published by a different npm account than previous versions on 2026-04-07. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.23
2 findingsThis version was published by a different npm account than previous versions on 2026-04-07. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.22
2 findingsThis version was published by a different npm account than previous versions on 2026-04-07. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.21
2 findingsThis version was published by a different npm account than previous versions on 2026-04-07. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.20
2 findingsThis version was published by a different npm account than previous versions on 2026-04-07. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.19
2 findingsThis version was published by a different npm account than previous versions on 2026-04-06. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.18
2 findingsThis version was published by a different npm account than previous versions on 2026-04-06. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.17
2 findingsThis version was published by a different npm account than previous versions on 2026-04-02. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.16
2 findingsThis version was published by a different npm account than previous versions on 2026-04-02. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.102
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.101
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.97
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.