← Home

@opra/common

Opra common package

16
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

erayhanogluilkergurelli

Keywords

opracommon

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): object-hash is a well-known package replacing a similar dep; benign swap. ai
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/http-parser AI (phantom-deps): Browser-only dep referenced in config; stable false positive for this package. ai
phantom-deps phantom-dep:@browsery/highland AI (phantom-deps): Browser-only dep referenced in config; stable false positive for this package. ai

Versions (showing 16 of 16)

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.6 15 / 0
1.17.5 15 / 0
1.15.1 14 / 0
1.0.7 16 / 0

v1.17.6

1 finding
INFO No provenance attestation provenance

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

v1.0.7

1 finding
INFO No provenance attestation provenance

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