@opra/client MIT 51 versions

@opra/client

npm Repository Homepage

Opra Client package

51

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

erayhanogluilkergurelli

Keywords

opranodeclientbrowserhttprequestfetch

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:browser.js	AI (source-diff): browser.js is the declared browser bundle entry point; minified output is expected for this package.	ai	2026/05/03
phantom-deps	phantom-dep:tslib	AI (phantom-deps): tslib is a known implicit runtime dep for TypeScript-compiled packages; stable false positive.	ai	2026/04/29
phantom-deps	phantom-dep:accepts	AI (phantom-deps): Referenced in config files only; not a direct import — stable false positive for this package.	ai	2026/04/29

Versions (showing 51 of 58)

View all versions

Version	Deps	Published
1.28.5	3 / 0	2026-05-20
1.28.4	3 / 0	2026-05-16
1.28.3	3 / 0	2026-05-14
1.28.2	3 / 0	2026-05-13
1.28.1	3 / 0	2026-05-12
1.28.0	3 / 0	2026-05-05
1.27.4	3 / 0	2026-04-29
1.27.2	3 / 0	2026-04-29
1.27.1	3 / 0	2026-04-27
1.27.0	3 / 0	2026-04-27
1.26.4	3 / 0	2026-04-17
1.26.3	3 / 0	2026-04-14
1.26.2	3 / 0	2026-04-14
1.26.1	3 / 0	2026-04-10
1.26.0	3 / 0	2026-04-10
1.25.6	3 / 0	2026-04-07
1.25.5	3 / 0	2026-04-07
1.25.4	3 / 0	2026-04-07
1.25.3	3 / 0	2026-04-06
1.25.2	3 / 0	2026-04-03
1.25.1	3 / 0	2026-04-03
1.24.4	3 / 0	2026-03-25
1.24.3	3 / 0	2026-03-25
1.24.2	3 / 0	2026-03-13
1.24.0	3 / 0	2026-03-11
1.23.3	3 / 0	2026-03-03
1.23.2	3 / 0	2026-02-12
1.23.0	3 / 0	2026-02-02
1.22.9	3 / 0	2026-01-27
1.22.8	3 / 0	2026-01-27
1.22.7	3 / 0	2026-01-22
1.22.6	3 / 0	2026-01-19
1.22.5	3 / 0	2026-01-14
1.22.4	3 / 0	2026-01-05
1.22.3	3 / 0	2026-01-02
1.22.2	3 / 0	2026-01-02
1.22.1	3 / 0	2025-12-29
1.22.0	3 / 0	2025-12-22
1.21.0	3 / 0	2025-12-08
1.20.0	3 / 0	2025-12-05
1.19.7	3 / 0	2025-11-03
1.19.5	3 / 0	2025-10-24
1.19.4	3 / 0	2025-08-15
1.19.3	3 / 0	2025-08-14
1.19.2	3 / 0	2025-07-30
1.19.1	3 / 0	2025-07-29
1.19.0	3 / 0	2025-07-24
1.17.7	3 / 0	2025-07-11
1.17.6	3 / 0	2025-06-23
1.17.5	3 / 0	2025-06-20
1.17.4	3 / 0	2025-06-13

v1.28.5

1 finding

LOW No provenance attestation provenance

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

v1.28.4

1 finding

LOW No provenance attestation provenance

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

v1.28.3

1 finding

LOW No provenance attestation provenance

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

v1.28.2

1 finding

LOW No provenance attestation provenance

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

v1.28.1

1 finding

LOW No provenance attestation provenance

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

v1.28.0

1 finding

LOW No provenance attestation provenance

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

v1.27.4

1 finding

LOW No provenance attestation provenance

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

v1.27.2

1 finding

LOW No provenance attestation provenance

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

v1.27.0

1 finding

LOW No provenance attestation provenance

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

v1.26.4

1 finding

LOW No provenance attestation provenance

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

v1.26.3

1 finding

LOW No provenance attestation provenance

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

v1.26.2

1 finding

LOW No provenance attestation provenance

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

v1.26.1

1 finding

LOW No provenance attestation provenance

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

v1.26.0

1 finding

LOW No provenance attestation provenance

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

v1.25.6

1 finding

LOW No provenance attestation provenance

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

v1.25.5

1 finding

LOW No provenance attestation provenance

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

v1.25.4

1 finding

LOW No provenance attestation provenance

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

v1.25.3

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.

v1.25.2

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.

v1.25.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.

v1.24.0

2 findings

HIGH New obfuscated file: browser.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.23.3

2 findings

HIGH New obfuscated file: browser.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.23.2

2 findings

HIGH New obfuscated file: browser.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.22.5

2 findings

HIGH New obfuscated file: browser.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.22.3

2 findings

HIGH New obfuscated file: browser.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.22.2

2 findings

HIGH New obfuscated file: browser.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.22.1

2 findings

HIGH New obfuscated file: browser.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.21.0

1 finding

LOW No provenance attestation provenance

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

v1.20.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.

v1.19.7

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.

v1.19.5

1 finding

LOW No provenance attestation provenance

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

v1.19.4

1 finding

LOW No provenance attestation provenance

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

v1.19.3

1 finding

LOW No provenance attestation provenance

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

v1.19.2

1 finding

LOW No provenance attestation provenance

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

v1.19.1

1 finding

LOW No provenance attestation provenance

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

v1.19.0

1 finding

LOW No provenance attestation provenance

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

v1.17.7

1 finding

LOW No provenance attestation provenance

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

v1.17.6

1 finding

LOW No provenance attestation provenance

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

v1.17.5

1 finding

LOW No provenance attestation provenance

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

v1.17.4

1 finding

LOW No provenance attestation provenance

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