@preply/ds-visual-coverage-rn No license 12 versions

@preply/ds-visual-coverage-rn

npm

12

Versions

—

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

preply-admineugenegodunerebus1alex.semeniukit-serviceserhii.tonkoshkurlukas-preplychinskiy_preply

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
bogus-package	bogus-package	AI (bogus-package): Internal @preply scoped design-system package; sparse metadata is expected for org-internal tooling across all versions.	ai	2026/05/04
npm-metadata	no-description	AI (npm-metadata): Consistent with internal tooling pattern across this package's 178 versions.	ai	2026/05/04

Versions (showing 12 of 12)

Version	Deps	Published
11.5.1	0 / 2	2026-05-28
11.5.0	0 / 2	2026-04-30
11.4.0	0 / 2	2026-04-23
11.3.0	0 / 2	2026-04-15
11.2.0	0 / 2	2026-04-07
8.0.0	0 / 2	2025-12-05
7.1.0	0 / 2	2025-11-20
7.0.0	0 / 2	2025-11-18
6.2.1	0 / 2	2025-11-18
6.2.0	0 / 2	2025-11-11
6.1.0	0 / 2	2025-11-07
6.0.0	0 / 2	2025-11-05

v11.5.1

1 finding

LOW No provenance attestation provenance

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

v11.5.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.

v11.4.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.

v11.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.

v11.2.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.

v8.0.0

1 finding

LOW No provenance attestation provenance

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

v7.1.0

1 finding

LOW No provenance attestation provenance

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

v7.0.0

1 finding

LOW No provenance attestation provenance

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

v6.2.1

1 finding

LOW No provenance attestation provenance

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

v6.2.0

1 finding

LOW No provenance attestation provenance

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

v6.1.0

1 finding

LOW No provenance attestation provenance

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

v6.0.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.