@sqlrooms/sql-editor MIT 44 versions

@sqlrooms/sql-editor

npm Repository Homepage

SQL editor UI and state slice for SQLRooms apps.

44

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

ilyabo

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:monaco-editor	AI (phantom-deps): monaco-editor is a peer of @monaco-editor/react; referenced in config but not directly imported — stable pattern for this package.	ai	2026/05/15
phantom-deps	phantom-dep:@sqlrooms/project-config	AI (phantom-deps): Same-org sibling dep in a monorepo; phantom-dep heuristic is a false positive here.	ai	2026/05/15
phantom-deps	phantom-dep:zustand	AI (phantom-deps): Monorepo package; zustand is a declared dep used transitively via sibling packages, not a direct import.	ai	2026/05/15
phantom-deps	phantom-dep:@sqlrooms/layout	AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is a stable false positive for this monorepo.	ai	2026/05/15
phantom-deps	phantom-dep:@sqlrooms/room-config	AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is a stable false positive for this monorepo.	ai	2026/05/15
phantom-deps	phantom-dep:@monaco-editor/react	AI (phantom-deps): @monaco-editor/react is explicitly declared in dependencies; phantom-dep is a false positive for this package.	ai	2026/04/28

Versions (showing 44 of 44)

Version	Deps	Published
0.28.0	19 / 4	2026-02-25
0.27.0	19 / 4	2026-02-20
0.26.0	22 / 4	2025-11-17
0.24.27	21 / 4	2025-09-26
0.24.26	21 / 4	2025-09-25
0.24.25	21 / 4	2025-09-23
0.24.24	20 / 4	2025-09-23
0.24.23	20 / 4	2025-09-17
0.24.22	20 / 4	2025-09-16
0.24.21	20 / 4	2025-09-11
0.24.20	20 / 4	2025-09-11
0.24.19	20 / 4	2025-09-09
0.24.18	20 / 4	2025-09-05
0.24.17	20 / 4	2025-09-03
0.24.16	20 / 4	2025-08-27
0.24.15	20 / 4	2025-08-27
0.24.14	20 / 4	2025-08-21
0.24.13	20 / 4	2025-08-21
0.24.12	20 / 4	2025-08-21
0.24.11	20 / 4	2025-08-07
0.24.10	20 / 4	2025-07-29
0.24.9	20 / 4	2025-07-28
0.24.8	20 / 4	2025-07-28
0.24.7	20 / 4	2025-07-28
0.24.6	20 / 4	2025-07-28
0.24.5	20 / 4	2025-07-25
0.24.4	20 / 4	2025-07-23
0.24.3	20 / 4	2025-07-20
0.24.2	20 / 4	2025-07-20
0.24.1	20 / 4	2025-07-20
0.24.0	20 / 4	2025-07-15
0.23.0	20 / 4	2025-07-10
0.22.0	20 / 4	2025-07-09
0.21.0	20 / 4	2025-07-06
0.20.0	20 / 4	2025-06-27
0.19.2	20 / 4	2025-06-23
0.19.1	20 / 4	2025-06-23
0.19.0	20 / 4	2025-06-23
0.18.1	19 / 4	2025-06-20
0.18.0	19 / 4	2025-06-19
0.17.0	19 / 4	2025-06-16
0.16.1	19 / 4	2025-06-11
0.13.1	19 / 4	2025-05-18
0.13.0	19 / 4	2025-05-13

v0.28.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.27.0

1 finding

LOW No provenance attestation provenance

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

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.24.27

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.26

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.25

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.24

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.23

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.22

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.24.21

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.20

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.19

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.23.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.22.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.21.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.20.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.19.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.19.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.19.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.18.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.18.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.16.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.13.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.13.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.