@ws-ui/shared No license 18 versions

@ws-ui/shared

npm

18

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

df_trainps-moim-4didrissimourad.eyesaxel-devanass00daalimouhcine

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@types/minimatch	AI (phantom-deps): Type-only package; convention-loaded, stable false positive for this package.	ai	2026/05/29
phantom-deps	phantom-dep:use-immer	AI (phantom-deps): Shared UI library; deps declared for consumers, not all directly imported in entry point.	ai	2026/05/27
phantom-deps	phantom-dep:classnames	AI (phantom-deps): Shared UI library; deps declared for consumers, not all directly imported in entry point.	ai	2026/05/27
phantom-deps	phantom-dep:jsonschema	AI (phantom-deps): Shared UI library; deps declared for consumers, not all directly imported in entry point.	ai	2026/05/27
phantom-deps	phantom-dep:short-uuid	AI (phantom-deps): Shared UI library; deps declared for consumers, not all directly imported in entry point.	ai	2026/05/27
phantom-deps	phantom-dep:marked-react	AI (phantom-deps): Shared UI library; deps declared for consumers, not all directly imported in entry point.	ai	2026/05/27
phantom-deps	phantom-dep:minimatch	AI (phantom-deps): Shared UI library; deps declared for consumers, not all directly imported in entry point.	ai	2026/05/27
phantom-deps	phantom-dep:markdown-to-jsx	AI (phantom-deps): Shared UI library; deps declared for consumers, not all directly imported in entry point.	ai	2026/05/27
phantom-deps	phantom-dep:@radix-ui/react-popover	AI (phantom-deps): Shared UI library; deps declared for consumers, not all directly imported in entry point.	ai	2026/05/27
phantom-deps	phantom-dep:@radix-ui/react-tooltip	AI (phantom-deps): Shared UI library; deps declared for consumers, not all directly imported in entry point.	ai	2026/05/27
phantom-deps	phantom-dep:react-responsive-carousel	AI (phantom-deps): Shared UI library; deps declared for consumers, not all directly imported in entry point.	ai	2026/05/27
phantom-deps	phantom-dep:react-popper	AI (phantom-deps): Shared UI library; deps declared for consumers, not all directly imported in entry point.	ai	2026/05/27

Versions (showing 18 of 18)

Version	Deps	Published
1.13.3	24 / 21	2026-06-04
1.13.2	24 / 21	2026-05-22
1.13.1	24 / 21	2026-05-20
1.13.0	24 / 21	2026-04-29
1.12.4	24 / 21	2026-04-10
1.12.3	24 / 21	2026-04-07
1.12.2	24 / 21	2026-04-07
1.12.1	24 / 21	2026-04-06
1.9.0	24 / 21	2025-12-10
1.8.5	24 / 21	2025-12-09
1.7.5	21 / 20	2025-11-06
1.6.10	21 / 20	2025-10-19
1.6.9	21 / 20	2025-10-15
1.5.7	5 / 26	2025-06-25
1.5.6	5 / 26	2025-06-23
1.5.5	5 / 26	2025-06-21
1.5.4	5 / 26	2025-05-18
1.5.3	5 / 26	2025-05-05

v1.13.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: axel-dev → idrissi (on 2026-06-04, known maintainer) provenance

This version was published by a different npm account (idrissi) than the most recent previously approved version (axel-dev) on 2026-06-04, but idrissi is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.13.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: axel-dev → idrissi (on 2026-05-22, known maintainer) provenance

This version was published by a different npm account (idrissi) than the most recent previously approved version (axel-dev) on 2026-05-22, but idrissi is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.13.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: axel-dev → idrissi (on 2026-05-20, known maintainer) provenance

This version was published by a different npm account (idrissi) than the most recent previously approved version (axel-dev) on 2026-05-20, but idrissi is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.13.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.

v1.12.4

1 finding

LOW No provenance attestation provenance

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

v1.12.3

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.

v1.12.2

1 finding

LOW No provenance attestation provenance

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

v1.12.1

1 finding

LOW No provenance attestation provenance

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

v1.9.0

1 finding

LOW No provenance attestation provenance

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

v1.8.5

1 finding

LOW No provenance attestation provenance

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

v1.7.5

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.

v1.6.10

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.

v1.6.9

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.

v1.5.7

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.

v1.5.6

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.

v1.5.5

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.

v1.5.4

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.

v1.5.3

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.