rrdom MIT 9 versions

rrdom

npm Repository Homepage

9

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

yanzhen

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:jsdom	AI (typosquat): rrdom is an intentional name in the rrweb ecosystem (rrweb DOM implementation), not a typosquat of jsdom. Stable false positive for this package.	ai	2026/04/24

Versions (showing 9 of 9)

Hide prereleases

Version	Deps	Published
0.1.7	1 / 15	2022-11-16
0.1.6	1 / 14	2022-09-30
0.1.5	1 / 14	2022-09-22
0.1.4	1 / 14	2022-07-31
0.1.3	1 / 14	2022-07-10
0.1.2	2 / 12	2022-04-04
0.1.1	2 / 12	2022-02-26
0.1.0	2 / 12	2022-01-23
2.0.0-alpha.20	1 / 9	2026-02-03

v0.1.7

1 finding

LOW No provenance attestation provenance

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

v0.1.6

1 finding

LOW No provenance attestation provenance

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

v0.1.5

1 finding

LOW No provenance attestation provenance

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

v0.1.4

1 finding

LOW No provenance attestation provenance

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

v0.1.3

1 finding

LOW No provenance attestation provenance

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

v0.1.2

1 finding

LOW No provenance attestation provenance

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

v0.1.1

1 finding

LOW No provenance attestation provenance

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

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