← Home

@openobserve/browser-rum-core

npm Repository Homepage

Openobserve browser RUM core utilities.

7
Versions
Apache-2.0
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

bhargav_ooprabhatsharmaprabhat_o2oasis_k

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@openobserve/js-core AI (dependencies): First-party sibling package from same org/monorepo, version-pinned. ai
source-diff large-new-source-files AI (source-diff): Monorepo restructure, not injected code; publisher track record is clean. ai
provenance missing-githead AI (provenance): Monorepo publish tooling variance, not a malicious signal. ai
publish-pattern new-deps-added AI (publish-pattern): uuid is a well-known, benign dependency for an SDK. ai
bogus-package bogus-package AI (bogus-package): Sparse README typical of internal monorepo sub-packages. ai

Versions (showing 7 of 7)

Version Deps Published
0.4.1 2 / 1
0.4.0 2 / 1
0.3.4 2 / 1
0.3.3 1 / 1
0.3.2 2 / 1
0.3.1 1 / 1
0.3.0 1 / 1

v0.4.1

1 finding
LOW No provenance attestation provenance

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

v0.4.0

2 findings
LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bhargav_oo.

v0.3.4

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bhargav_oo.

LOW No provenance attestation provenance

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

v0.3.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.

v0.3.2

1 finding
LOW No provenance attestation provenance

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

v0.3.1

1 finding
LOW No provenance attestation provenance

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

v0.3.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.