@preply/ds-rn-lib
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@radix-ui/react-slot | AI (phantom-deps): Declared in dependencies; used by library components. False positive for scoped packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo internal package; missing metadata is expected and not indicative of malice. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 11.5.1 | 1 / 30 | |
| 11.5.0 | 1 / 30 | |
| 11.4.0 | 1 / 30 | |
| 11.3.0 | 1 / 30 | |
| 11.2.0 | 1 / 30 | |
| 8.0.0 | 1 / 30 | |
| 7.1.0 | 1 / 28 | |
| 7.0.0 | 1 / 28 | |
| 6.2.1 | 1 / 28 | |
| 6.2.0 | 1 / 28 | |
| 6.1.0 | 1 / 28 | |
| 6.0.0 | 1 / 28 |
v11.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.