@sqlrooms/room-shell
Main SQLRooms application shell and default Room slice composition.
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:zod | AI (phantom-deps): Monorepo package; zod referenced in config/type files, not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:apache-arrow | AI (phantom-deps): Monorepo package; apache-arrow referenced in config files, stable false positive. | ai | |
| phantom-deps | phantom-dep:react-mosaic-component | AI (phantom-deps): Monorepo package; referenced in config files, stable false positive. | ai | |
| phantom-deps | phantom-dep:@sqlrooms/layout-config | AI (phantom-deps): Same-org monorepo sibling; stable false positive for this package. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 0.28.0 | 14 / 0 | |
| 0.27.0 | 12 / 0 | |
| 0.26.0 | 14 / 0 | |
| 0.24.27 | 14 / 0 | |
| 0.24.26 | 14 / 0 | |
| 0.24.25 | 14 / 0 | |
| 0.24.24 | 14 / 0 | |
| 0.24.23 | 14 / 0 | |
| 0.24.22 | 14 / 0 | |
| 0.24.21 | 14 / 0 | |
| 0.24.20 | 14 / 0 | |
| 0.24.19 | 14 / 0 | |
| 0.24.18 | 14 / 0 | |
| 0.24.17 | 14 / 0 | |
| 0.24.16 | 14 / 0 | |
| 0.24.15 | 14 / 0 | |
| 0.24.14 | 14 / 0 | |
| 0.24.13 | 14 / 0 | |
| 0.24.12 | 14 / 0 | |
| 0.24.11 | 14 / 0 | |
| 0.24.10 | 14 / 0 | |
| 0.24.9 | 14 / 0 | |
| 0.24.8 | 14 / 0 | |
| 0.24.7 | 14 / 0 | |
| 0.24.6 | 14 / 0 | |
| 0.24.5 | 14 / 0 | |
| 0.24.4 | 14 / 0 | |
| 0.24.3 | 14 / 0 | |
| 0.24.2 | 14 / 0 | |
| 0.24.1 | 14 / 0 | |
| 0.24.0 | 14 / 0 | |
| 0.23.0 | 14 / 0 | |
| 0.22.0 | 14 / 0 | |
| 0.21.0 | 14 / 0 | |
| 0.20.0 | 14 / 0 | |
| 0.19.2 | 14 / 0 | |
| 0.19.1 | 14 / 0 | |
| 0.19.0 | 14 / 0 | |
| 0.18.1 | 13 / 0 | |
| 0.18.0 | 13 / 0 | |
| 0.17.0 | 13 / 0 |
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.