@peculiar/react-components MIT 23 versions

@peculiar/react-components

npm Repository Homepage

A simple and customizable component library to build faster, beautiful, and more accessible React applications.

23

Versions

MIT

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

rmhriskmicroshineyury.strozhevskypeculiarventuresapilgukdonskovworldthirteen

Keywords

reactreact-component

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@types/flat	AI (phantom-deps): @types/flat is a type declaration package used by convention; not directly imported but legitimately needed.	ai	2026/05/15
phantom-deps	phantom-dep:@types/react-transition-group	AI (phantom-deps): @types/react-transition-group is a type declaration package used by convention; stable false positive for this package.	ai	2026/05/15

Versions (showing 23 of 23)

Version	Deps	Published
1.8.9	12 / 12	2026-04-29
1.8.8	12 / 12	2026-04-22
1.8.7	12 / 12	2026-04-02
1.8.6	12 / 12	2026-03-23
1.8.5	12 / 12	2026-03-18
1.8.4	12 / 12	2026-03-11
1.8.3	12 / 12	2026-03-11
1.8.2	12 / 12	2026-03-02
1.8.1	12 / 12	2026-02-25
1.8.0	12 / 12	2026-02-18
1.7.0	12 / 12	2025-12-22
1.6.1	12 / 12	2025-12-04
1.6.0	12 / 12	2025-12-02
1.5.3	12 / 12	2025-10-23
1.5.2	12 / 14	2025-10-09
1.5.1	12 / 14	2025-09-15
1.5.0	12 / 14	2025-08-20
1.4.0	12 / 14	2025-08-19
1.3.2	12 / 14	2025-08-12
1.3.1	12 / 14	2025-08-11
1.3.0	12 / 14	2025-08-11
1.2.0	12 / 14	2025-08-11
1.1.3	12 / 14	2025-07-09

v1.8.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.8.8

1 finding

LOW No provenance attestation provenance

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

v1.8.7

1 finding

LOW No provenance attestation provenance

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

v1.8.6

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

1 finding

LOW No provenance attestation provenance

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

v1.8.3

1 finding

LOW No provenance attestation provenance

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

v1.8.2

1 finding

LOW No provenance attestation provenance

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

v1.8.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.8.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.7.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.6.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.6.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.5.3

1 finding

LOW No provenance attestation provenance

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

v1.5.2

1 finding

LOW No provenance attestation provenance

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

v1.5.1

1 finding

LOW No provenance attestation provenance

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

v1.5.0

1 finding

LOW No provenance attestation provenance

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

v1.4.0

1 finding

LOW No provenance attestation provenance

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

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

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

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