@preply/ds-docs
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal design-system docs package in @preply scope; 541 versions, 1612 days old — metadata signals are false positives for private tooling. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal scoped package; missing description is expected for private tooling. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 11.5.0 | 0 / 25 | |
| 11.4.0 | 0 / 25 | |
| 11.3.0 | 0 / 25 | |
| 11.2.0 | 0 / 24 |
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.