@clinebot/llms
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): @ai-sdk/provider is official Vercel AI SDK package, consistent with existing deps. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Publisher is a known maintainer per provenance record, not a takeover. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Monorepo workspace package using 0.0.0 as a placeholder version; 34 published versions confirm legitimate project. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decoding image data from Bedrock API responses; standard multimodal provider pattern, not a payload risk. | ai | |
| phantom-deps | phantom-dep:ai | AI (phantom-deps): Config-driven provider SDK; deps loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/google | AI (phantom-deps): Provider plugin pattern; loaded by convention. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/openai | AI (phantom-deps): Provider plugin pattern; loaded by convention. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/anthropic | AI (phantom-deps): Provider plugin pattern; loaded by convention. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/openai-compatible | AI (phantom-deps): Provider plugin pattern; loaded by convention. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/google-vertex | AI (phantom-deps): Provider plugin pattern; loaded by convention. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/mistral | AI (phantom-deps): Provider loaded by convention in config-driven architecture. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/amazon-bedrock | AI (phantom-deps): Provider loaded by convention in config-driven architecture. | ai | |
| phantom-deps | phantom-dep:@streamparser/json | AI (phantom-deps): Utility dep used indirectly; consistent with config-driven provider pattern. | ai | |
| phantom-deps | phantom-dep:dify-ai-provider | AI (phantom-deps): Provider loaded by convention in config-driven architecture. | ai | |
| phantom-deps | phantom-dep:ai-sdk-provider-codex-cli | AI (phantom-deps): Provider loaded by convention in config-driven architecture. | ai | |
| phantom-deps | phantom-dep:ai-sdk-provider-claude-code | AI (phantom-deps): Provider loaded by convention in config-driven architecture. | ai | |
| phantom-deps | phantom-dep:ai-sdk-provider-opencode-sdk | AI (phantom-deps): Provider loaded by convention in config-driven architecture. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/credential-providers | AI (phantom-deps): Framework-scoped AWS credential package; loaded by convention as noted by analyzer. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): Config-driven provider library; deps loaded by convention, not direct import. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 0.0.38 | 21 / 0 | |
| 0.0.37 | 21 / 0 | |
| 0.0.36 | 20 / 0 | |
| 0.0.35 | 20 / 0 | |
| 0.0.34 | 20 / 0 | |
| 0.0.33 | 20 / 0 | |
| 0.0.32 | 20 / 0 | |
| 0.0.31 | 20 / 0 | |
| 0.0.30 | 20 / 0 | |
| 0.0.29 | 20 / 0 | |
| 0.0.28 | 17 / 0 | |
| 0.0.27 | 17 / 0 | |
| 0.0.26 | 17 / 0 | |
| 0.0.25 | 17 / 0 | |
| 0.0.24 | 16 / 0 | |
| 0.0.23 | 16 / 0 | |
| 0.0.22 | 16 / 0 | |
| 0.0.21 | 16 / 0 | |
| 0.0.20 | 16 / 0 | |
| 0.0.18 | 16 / 0 | |
| 0.0.16 | 16 / 0 | |
| 0.0.15 | 16 / 0 | |
| 0.0.14 | 16 / 0 | |
| 0.0.13 | 16 / 0 | |
| 0.0.12 | 16 / 0 | |
| 0.0.11 | 16 / 0 | |
| 0.0.10 | 16 / 0 | |
| 0.0.7 | 15 / 0 | |
| 0.0.6 | 15 / 0 | |
| 0.0.5 | 15 / 0 | |
| 0.0.4 | 15 / 0 | |
| 0.0.3 | 15 / 0 | |
| 0.0.2 | 15 / 0 | |
| 0.0.1 | 16 / 0 | |
| 0.0.0 | 16 / 0 |
v0.0.38
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (beatrix-cline) than the most recent previously approved version (barreirot) on 2026-05-05, but beatrix-cline is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.37
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (beatrix-cline) than the most recent previously approved version (barreirot) on 2026-04-28, but beatrix-cline is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (beatrix-cline) than the most recent previously approved version (barreirot) on 2026-04-21, but beatrix-cline is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.34
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (beatrix-cline) than the most recent previously approved version (barreirot) on 2026-04-14, but beatrix-cline is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.31
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (barreirot) than the most recent previously approved version (beatrix-cline) on 2026-04-11, but barreirot is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.