@sqlrooms/s3-browser
This package is part of the SQLRooms framework.
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 | dormant-publish | AI (publish-pattern): Publisher has 140 approved packages; dormancy reflects monorepo release cadence, not account takeover. | ai | |
| dependencies | unvetted-dep:@sqlrooms/room-shell | AI (dependencies): First-party @sqlrooms monorepo package published at the same version; not a third-party risk. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo package; lack of provenance is consistent across all sqlrooms releases. | ai |
Versions (showing 73 of 73)
| Version | Deps | Published |
|---|---|---|
| 0.28.0 | 10 / 0 | |
| 0.27.0 | 10 / 0 | |
| 0.26.0 | 5 / 0 | |
| 0.24.27 | 5 / 0 | |
| 0.24.26 | 5 / 0 | |
| 0.24.25 | 5 / 0 | |
| 0.24.24 | 5 / 0 | |
| 0.24.23 | 5 / 0 | |
| 0.24.22 | 5 / 0 | |
| 0.24.21 | 5 / 0 | |
| 0.24.20 | 5 / 0 | |
| 0.24.19 | 5 / 0 | |
| 0.24.18 | 5 / 0 | |
| 0.24.17 | 5 / 0 | |
| 0.24.16 | 5 / 0 | |
| 0.24.15 | 5 / 0 | |
| 0.24.14 | 5 / 0 | |
| 0.24.13 | 5 / 0 | |
| 0.24.12 | 5 / 0 | |
| 0.24.11 | 5 / 0 | |
| 0.24.10 | 5 / 0 | |
| 0.24.9 | 5 / 0 | |
| 0.24.8 | 5 / 0 | |
| 0.24.7 | 5 / 0 | |
| 0.24.6 | 5 / 0 | |
| 0.24.5 | 5 / 0 | |
| 0.24.4 | 5 / 0 | |
| 0.24.3 | 5 / 0 | |
| 0.24.2 | 5 / 0 | |
| 0.24.1 | 5 / 0 | |
| 0.24.0 | 5 / 0 | |
| 0.23.0 | 5 / 0 | |
| 0.22.0 | 5 / 0 | |
| 0.21.0 | 5 / 0 | |
| 0.20.0 | 5 / 0 | |
| 0.19.2 | 5 / 0 | |
| 0.19.1 | 5 / 0 | |
| 0.19.0 | 5 / 0 | |
| 0.18.1 | 5 / 0 | |
| 0.18.0 | 5 / 0 | |
| 0.17.0 | 5 / 0 | |
| 0.16.4 | 5 / 0 | |
| 0.16.3 | 5 / 0 | |
| 0.16.2 | 5 / 0 | |
| 0.16.1 | 5 / 0 | |
| 0.16.0 | 5 / 0 | |
| 0.15.0 | 5 / 0 | |
| 0.14.0 | 5 / 0 | |
| 0.13.2 | 5 / 0 | |
| 0.13.1 | 5 / 0 | |
| 0.13.0 | 5 / 0 | |
| 0.12.0 | 5 / 0 | |
| 0.11.0 | 5 / 0 | |
| 0.10.1 | 5 / 0 | |
| 0.10.0 | 5 / 0 | |
| 0.9.3 | 5 / 0 | |
| 0.9.2 | 5 / 0 | |
| 0.9.1 | 5 / 0 | |
| 0.9.0 | 5 / 0 | |
| 0.8.1 | 5 / 0 | |
| 0.8.0 | 5 / 0 | |
| 0.7.0 | 5 / 0 | |
| 0.6.0 | 5 / 0 | |
| 0.5.1 | 5 / 0 | |
| 0.5.0 | 5 / 0 | |
| 0.4.2 | 5 / 0 | |
| 0.4.1 | 5 / 0 | |
| 0.4.0 | 5 / 0 | |
| 0.3.0 | 5 / 0 | |
| 0.1.0 | 5 / 0 | |
| 0.0.3 | 5 / 0 | |
| 0.0.2 | 5 / 0 | |
| 0.0.1 | 5 / 0 |
v0.12.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.11.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.10.1
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.10.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.9.3
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.9.2
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.9.1
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.9.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.8.1
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.8.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.7.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.6.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.5.1
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.5.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.4.2
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.4.1
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.4.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.3.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.1.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.0.3
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.0.2
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.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.