@slowcook-ai/llm-anthropic
Anthropic (Claude) LlmClient adapter for slowcook — implements the core LlmClient interface, provider-specific pricing, and Anthropic-tuned system prompts + tool defs for refine / testgen / brew / sift / investigate agents
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/prompts/orchestrate.d.ts | AI (source-diff): Long lines are LLM system prompt strings in .d.ts declaration files — readable, not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/prompts/chef.d.ts | AI (source-diff): Long lines are LLM system prompt strings in .d.ts files, not obfuscated code. Stable pattern for this package. | ai | |
| source-diff | obfuscated-file:dist/prompts/navigator.d.ts | AI (source-diff): Long lines are LLM system prompt strings in .d.ts files, not obfuscated code. Stable pattern for this package. | ai | |
| source-diff | obfuscated-file:dist/prompts/sift.d.ts | AI (source-diff): Long lines are LLM system prompt strings in TypeScript declaration files — readable prose, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/prompts/brew.d.ts | AI (source-diff): Long lines are LLM system prompt strings in TypeScript declaration files — readable prose, not obfuscated code. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is from new prompt string files; benign for this package. | ai | |
| source-diff | obfuscated-file:dist/prompts/investigate.d.ts | AI (source-diff): Long lines are LLM system prompt strings in TypeScript declaration files — readable prose, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/prompts/refine.d.ts | AI (source-diff): Long lines are LLM system prompt strings in TypeScript declaration files — readable prose, not obfuscated code. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.16.3 | 2 / 1 | |
| 0.16.2 | 2 / 1 | |
| 0.16.1 | 2 / 1 | |
| 0.16.0 | 2 / 1 | |
| 0.15.0 | 2 / 0 | |
| 0.14.1 | 2 / 0 | |
| 0.14.0 | 2 / 0 | |
| 0.13.7 | 2 / 0 | |
| 0.13.6 | 2 / 0 | |
| 0.13.5 | 2 / 0 | |
| 0.13.1 | 2 / 0 | |
| 0.13.0 | 2 / 0 | |
| 0.12.4 | 2 / 0 | |
| 0.12.3 | 2 / 0 | |
| 0.12.1 | 2 / 0 | |
| 0.12.0 | 2 / 0 | |
| 0.11.1 | 2 / 0 | |
| 0.11.0 | 2 / 0 | |
| 0.10.0 | 2 / 0 | |
| 0.9.0 | 2 / 0 | |
| 0.8.1 | 2 / 0 | |
| 0.8.0 | 2 / 0 |
v0.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
4 findingsNewly 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.
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.16.0
4 findingsNewly 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.
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.15.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 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.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.