@preply/ds-ai-core
Shared AI tools for the Preply Design System
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:glob | AI (phantom-deps): glob is a declared runtime dependency; phantom-dep heuristic misfires on indirect/dynamic usage patterns. | ai | |
| phantom-deps | phantom-dep:zod-opts | AI (phantom-deps): zod-opts is a declared runtime dependency; phantom-dep heuristic misfires on indirect/dynamic usage patterns. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 12.0.0 | 10 / 9 | |
| 11.5.1 | 10 / 9 | |
| 11.5.0 | 10 / 9 | |
| 11.4.0 | 10 / 9 | |
| 11.3.0 | 10 / 9 | |
| 11.2.0 | 10 / 9 | |
| 11.1.0 | 10 / 9 |
v12.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.