← Home

@preply/ds-web-lib

npm
10
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.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Preply internal design system package; provenance not configured in their CI pipeline across all versions. ai
dependencies unvetted-dep:@base-ui-components/react AI (dependencies): Known MUI/Base UI project; beta version constraint is intentional for this design-system package. ai
phantom-deps phantom-dep:react-is AI (phantom-deps): Declared in deps and @types in devDeps; used indirectly via config/barrel pattern. ai
phantom-deps phantom-dep:@react-aria/focus AI (phantom-deps): Component library dependency; phantom-dep heuristic unreliable for bundled libs. ai
phantom-deps phantom-dep:usehooks-ts AI (phantom-deps): Component library dependency; phantom-dep heuristic unreliable for bundled libs. ai
phantom-deps phantom-dep:sonner AI (phantom-deps): Component library likely re-exports or uses in config; stable false positive for this package. ai
bogus-package bogus-package AI (bogus-package): Scoped internal design-system library; missing metadata is expected for org-internal packages. ai
npm-metadata no-description AI (npm-metadata): Internal scoped package; missing description is consistent across all versions. ai

Versions (showing 10 of 10)

Version Deps Published
11.5.0 5 / 19
11.4.0 5 / 19
11.3.0 5 / 19
11.2.0 5 / 19
8.0.0 6 / 19
7.1.0 6 / 19
6.2.1 6 / 19
6.2.0 6 / 19
6.1.0 6 / 19
6.0.0 6 / 19

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.

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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

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.