@opra/common
Opra common 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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@browsery/antlr4 | AI (dependencies): @browsery/* are scoped packages from the same panates/opra ecosystem; stable dependency across many versions. | ai | |
| dependencies | unvetted-dep:@browsery/highland | AI (dependencies): @browsery/* are scoped packages from the same panates/opra ecosystem; stable dependency across many versions. | ai | |
| provenance | no-provenance | AI (provenance): Long-established package with no provenance history; consistent across all 242 versions. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Fires inside bundled ANTLR4 parser code; not a payload loader pattern. | ai | |
| phantom-deps | phantom-dep:@browsery/highland | AI (phantom-deps): Browser-only dep referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@browsery/http-parser | AI (phantom-deps): Browser-only dep referenced in config; stable false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.28.0 | 15 / 0 | |
| 1.27.4 | 15 / 0 | |
| 1.27.2 | 15 / 0 | |
| 1.27.1 | 15 / 0 | |
| 1.26.4 | 15 / 0 | |
| 1.26.3 | 15 / 0 | |
| 1.26.1 | 15 / 0 | |
| 1.25.6 | 15 / 0 | |
| 1.25.4 | 15 / 0 | |
| 1.25.1 | 15 / 0 | |
| 1.22.0 | 15 / 0 | |
| 1.20.0 | 15 / 0 | |
| 1.17.5 | 15 / 0 | |
| 1.15.1 | 14 / 0 |
v1.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.