@sqlrooms/ai-settings
AI provider/model settings state and UI components for SQLRooms.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@sqlrooms/room-config | AI (phantom-deps): Same-org scoped dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:ai | AI (phantom-deps): Config-driven dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Config-driven dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:rehype-raw | AI (phantom-deps): Config-driven dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:remark-gfm | AI (phantom-deps): Config-driven dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:react-markdown | AI (phantom-deps): Config-driven dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@sqlrooms/utils | AI (phantom-deps): Same-org scoped dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/provider | AI (phantom-deps): Config-driven dependency; stable pattern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all sqlrooms monorepo packages; not a per-version risk signal. | ai |
v0.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.