@darajs/ui-widgets Apache-2.0 56 versions

@darajs/ui-widgets

npm Repository Homepage

The UI widgets built on top of UI components

56

Versions

Apache-2.0

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

krzysztof-causalens

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Transition from human publisher to GitHub Actions CI is expected for a monorepo adopting SLSA provenance; SLSA attestation confirms integrity.	ai	2026/05/06
publish-pattern	dormant-publish	AI (publish-pattern): Dormancy followed by CI-published release with SLSA attestation and no material changes; consistent with a legitimate release cadence change.	ai	2026/05/06
phantom-deps	phantom-dep:react-dom	AI (phantom-deps): Declared as runtime dep; phantom-dep heuristic false positive for config-referenced packages.	ai	2026/04/30
phantom-deps	phantom-dep:lodash	AI (phantom-deps): Declared as runtime dep; referenced in config files is a known heuristic false positive for this monorepo package.	ai	2026/04/30
phantom-deps	phantom-dep:@darajs/ui-utils	AI (phantom-deps): Same-org monorepo package; stable false positive for this package.	ai	2026/04/30
phantom-deps	phantom-dep:@darajs/ui-icons	AI (phantom-deps): Same-org monorepo package; stable false positive for this package.	ai	2026/04/30
phantom-deps	phantom-dep:nanoid	AI (phantom-deps): Declared as runtime dep; phantom-dep heuristic false positive for config-referenced packages.	ai	2026/04/30

Versions (showing 56 of 156)

Version	Deps	Published
1.16.15	8 / 30	2025-06-02
1.16.14	8 / 30	2025-05-28
1.16.13	8 / 30	2025-05-27
1.16.12	8 / 30	2025-05-21
1.16.11	8 / 30	2025-05-20
1.16.10	8 / 30	2025-05-19
1.16.9	8 / 30	2025-05-01
1.16.8	8 / 30	2025-04-25
1.16.7	8 / 30	2025-04-24
1.16.6	8 / 30	2025-04-22
1.16.5	8 / 30	2025-04-16
1.16.4	8 / 30	2025-04-16
1.16.3	8 / 30	2025-04-15
1.16.2	8 / 30	2025-04-14
1.16.1	8 / 30	2025-04-10
1.16.0	8 / 30	2025-04-10
1.15.7	8 / 30	2025-04-07
1.15.6	8 / 30	2025-04-03
1.15.5	8 / 30	2025-03-18
1.15.4	8 / 30	2025-03-10
1.15.3	8 / 30	2025-03-04
1.15.2	8 / 30	2025-02-27
1.15.1	8 / 30	2025-02-26
1.15.0	8 / 30	2025-02-12
1.14.9	8 / 30	2025-01-31
1.14.8	8 / 30	2024-12-23
1.14.7	8 / 30	2024-12-17
1.14.6	8 / 30	2024-12-09
1.14.5	8 / 30	2024-12-03
1.14.4	8 / 30	2024-11-22
1.14.3	8 / 30	2024-11-08
1.14.2	8 / 30	2024-10-28
1.14.1	8 / 30	2024-10-25
1.14.0	8 / 30	2024-10-25
1.13.1	8 / 30	2024-10-14
1.13.0	8 / 30	2024-09-12
1.12.7	8 / 30	2024-08-23
1.12.6	8 / 30	2024-08-16
1.12.5	8 / 30	2024-08-15
1.12.4	8 / 30	2024-08-07
1.12.3	8 / 30	2024-08-06
1.12.2	8 / 30	2024-08-05
1.12.1	8 / 30	2024-08-02
1.11.5	8 / 30	2024-07-29
1.11.4	8 / 30	2024-07-26
1.11.3	8 / 30	2024-07-22
1.11.2	8 / 30	2024-07-10
1.10.3	8 / 30	2024-07-03
1.10.2	8 / 30	2024-06-26
1.10.1	8 / 30	2024-06-20
1.10.0	8 / 30	2024-06-11
1.9.6	8 / 30	2024-06-05
1.9.5	8 / 30	2024-05-20
1.9.4	8 / 30	2024-05-16
1.9.3	8 / 30	2024-05-14
1.9.2	8 / 30	2024-05-02

v1.16.8

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.16.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.16.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.16.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.16.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.16.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.16.2

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

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.16.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.15.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.15.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.15.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.15.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.15.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.15.2

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

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.15.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.14.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.14.8

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.14.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.14.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.14.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.14.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.14.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.14.2

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

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.14.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.13.1

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

v1.12.1

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.11.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.11.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.11.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.11.2

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

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

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.10.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.9.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.9.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.9.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.9.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.9.2

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.