@opra/sqb
Opra SQB adapter package
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package in established opra monorepo; name similarity to 'qs' is coincidental. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit TypeScript runtime dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:reflect-metadata | AI (phantom-deps): reflect-metadata is a known implicit decorator polyfill dep; stable false positive for this package. | ai |
Versions (showing 100 of 117)
| Version | Deps | Published |
|---|---|---|
| 1.29.2 | 3 / 0 | |
| 1.29.1 | 3 / 0 | |
| 1.29.0 | 3 / 0 | |
| 1.28.5 | 3 / 0 | |
| 1.28.4 | 3 / 0 | |
| 1.28.3 | 3 / 0 | |
| 1.28.2 | 3 / 0 | |
| 1.28.1 | 3 / 0 | |
| 1.28.0 | 3 / 0 | |
| 1.27.4 | 3 / 0 | |
| 1.27.2 | 3 / 0 | |
| 1.27.1 | 3 / 0 | |
| 1.27.0 | 3 / 0 | |
| 1.26.4 | 3 / 0 | |
| 1.26.3 | 3 / 0 | |
| 1.26.2 | 3 / 0 | |
| 1.26.1 | 3 / 0 | |
| 1.26.0 | 3 / 0 | |
| 1.25.6 | 3 / 0 | |
| 1.25.5 | 3 / 0 | |
| 1.25.4 | 3 / 0 | |
| 1.25.3 | 3 / 0 | |
| 1.25.2 | 3 / 0 | |
| 1.25.1 | 3 / 0 | |
| 1.24.4 | 3 / 0 | |
| 1.24.3 | 3 / 0 | |
| 1.24.2 | 3 / 0 | |
| 1.24.0 | 3 / 0 | |
| 1.23.3 | 3 / 0 | |
| 1.23.2 | 3 / 0 | |
| 1.23.0 | 3 / 0 | |
| 1.22.9 | 3 / 0 | |
| 1.22.8 | 3 / 0 | |
| 1.22.7 | 3 / 0 | |
| 1.22.6 | 3 / 0 | |
| 1.22.5 | 3 / 0 | |
| 1.22.4 | 3 / 0 | |
| 1.22.3 | 3 / 0 | |
| 1.22.2 | 3 / 0 | |
| 1.22.1 | 3 / 0 | |
| 1.22.0 | 3 / 0 | |
| 1.21.0 | 3 / 0 | |
| 1.20.0 | 3 / 0 | |
| 1.19.7 | 3 / 0 | |
| 1.19.5 | 3 / 0 | |
| 1.19.4 | 3 / 0 | |
| 1.19.3 | 3 / 0 | |
| 1.19.2 | 3 / 0 | |
| 1.19.1 | 3 / 0 | |
| 1.19.0 | 3 / 0 | |
| 1.17.7 | 3 / 0 | |
| 1.17.6 | 3 / 0 | |
| 1.17.5 | 3 / 0 | |
| 1.17.4 | 3 / 0 | |
| 1.17.3 | 3 / 0 | |
| 1.17.2 | 3 / 0 | |
| 1.17.1 | 3 / 0 | |
| 1.17.0 | 3 / 0 | |
| 1.16.1 | 3 / 0 | |
| 1.16.0 | 3 / 0 | |
| 1.15.1 | 3 / 0 | |
| 1.15.0 | 3 / 0 | |
| 1.14.0 | 3 / 0 | |
| 1.13.0 | 3 / 0 | |
| 1.12.6 | 3 / 0 | |
| 1.12.5 | 3 / 0 | |
| 1.12.4 | 3 / 0 | |
| 1.12.3 | 3 / 0 | |
| 1.12.2 | 3 / 0 | |
| 1.12.1 | 3 / 0 | |
| 1.12.0 | 3 / 0 | |
| 1.11.1 | 3 / 0 | |
| 1.11.0 | 3 / 0 | |
| 1.10.0 | 3 / 0 | |
| 1.9.4 | 3 / 0 | |
| 1.9.3 | 3 / 0 | |
| 1.9.2 | 3 / 0 | |
| 1.9.1 | 3 / 0 | |
| 1.9.0 | 3 / 0 | |
| 1.8.0 | 3 / 0 | |
| 1.7.4 | 3 / 0 | |
| 1.7.3 | 3 / 0 | |
| 1.7.2 | 3 / 0 | |
| 1.7.1 | 3 / 0 | |
| 1.7.0 | 3 / 0 | |
| 1.6.0 | 3 / 0 | |
| 1.5.7 | 3 / 0 | |
| 1.5.6 | 3 / 0 | |
| 1.5.5 | 3 / 0 | |
| 1.5.4 | 3 / 0 | |
| 1.5.3 | 3 / 0 | |
| 1.5.2 | 3 / 0 | |
| 1.5.1 | 3 / 0 | |
| 1.5.0 | 3 / 0 | |
| 1.4.4 | 3 / 0 | |
| 1.4.3 | 3 / 0 | |
| 1.4.2 | 3 / 0 | |
| 1.4.1 | 3 / 0 | |
| 1.4.0 | 3 / 0 | |
| 1.3.1 | 3 / 0 |
v1.29.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.