@rspack/plugin-react-refresh MIT 66 versions

@rspack/plugin-react-refresh

npm Repository

React refresh plugin for Rspack

66

Versions

MIT

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

hardfistchenjiahan

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher changed to GitHub Actions with SLSA provenance attestation, indicating a legitimate migration to automated CI/CD releases. This is expected and desirable for this established package.	ai	2026/04/24
bogus-package	bogus-package	AI (bogus-package): Part of the rspack monorepo (@rspack/* namespace); mass-production signal reflects legitimate monorepo publishing pattern, not spam. Sparse README is typical for ecosystem sub-packages.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Established rspack ecosystem package; lack of provenance is common and not a risk signal for this well-known project.	ai	2026/04/24

Versions (showing 66 of 66)

Hide prereleases

Version	Deps	Published
2.0.1	0 / 9	2026-05-28
2.0.0	0 / 9	2026-04-08
1.6.2	1 / 16	2026-04-07
1.6.1	2 / 16	2026-02-12
1.6.0	2 / 16	2026-01-07
1.5.3	2 / 16	2025-11-12
1.5.2	2 / 20	2025-10-21
1.5.1	2 / 20	2025-09-08
1.5.0	2 / 18	2025-08-28
1.4.3	2 / 19	2025-05-12
1.4.2	2 / 19	2025-05-07
1.4.1	2 / 19	2025-04-23
1.4.0	2 / 19	2025-04-23
1.3.1	2 / 18	2025-04-23
1.3.0	2 / 18	2025-04-22
1.2.2	2 / 18	2025-04-21
1.2.1	2 / 18	2025-04-15
1.2.0	2 / 18	2025-04-07
1.1.1	2 / 18	2025-04-06
1.1.0	2 / 18	2025-04-02
1.0.3	2 / 18	2025-01-25
1.0.2	3 / 17	2025-01-23
1.0.1	2 / 16	2024-12-10
1.0.0	2 / 16	2024-08-10
0.7.5	0 / 3	2024-06-25
0.7.4	0 / 3	2024-06-18
0.7.3	0 / 3	2024-06-13
0.7.2	0 / 3	2024-06-11
0.7.1	0 / 3	2024-06-05
0.7.0	0 / 3	2024-05-28
0.6.5	0 / 3	2024-05-08
0.6.4	0 / 3	2024-05-07
0.6.3	0 / 3	2024-04-23
0.6.2	0 / 3	2024-04-17
0.6.1	0 / 3	2024-04-11
0.6.0	0 / 3	2024-04-09
0.5.9	0 / 3	2024-03-26
0.5.8	0 / 3	2024-03-19
0.5.7	0 / 3	2024-03-12
0.5.6	0 / 3	2024-03-05
0.5.5	0 / 3	2024-02-27
0.5.4	0 / 3	2024-02-06
0.5.3	0 / 3	2024-01-29
0.5.2	0 / 3	2024-01-23
0.5.1	0 / 3	2024-01-16
0.5.0	0 / 3	2024-01-09
0.4.5	0 / 3	2023-12-26
0.4.4	0 / 3	2023-12-20
0.4.3	0 / 3	2023-12-12
0.4.2	0 / 3	2023-12-05
0.4.1	1 / 3	2023-11-28
0.4.0	1 / 3	2023-11-22
0.3.14	1 / 3	2023-11-17
0.3.13	1 / 3	2023-11-15
0.3.12	1 / 3	2023-11-14
0.3.11	2 / 3	2023-11-07
0.3.10	2 / 3	2023-11-02
0.3.9	2 / 3	2023-11-02
0.3.8	2 / 3	2023-10-24
0.3.7	2 / 3	2023-10-17
0.3.6	2 / 3	2023-10-02
0.3.5	2 / 3	2023-09-26
0.3.4	1 / 1	2023-09-13
0.3.3	1 / 1	2023-09-13
0.3.1	1 / 1	2023-09-10
2.0.0-beta.0	0 / 9	2026-04-08

v2.0.1

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.0.0

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.6.2

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.6.1

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.6.0

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.5.3

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.5.2

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.5.1

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.5.0

2 findings

HIGH Publisher changed: hardfist → GitHub Actions (on 2025-08-28) provenance

This version was published by a different npm account than previous versions on 2025-08-28. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.4.3

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.4.2

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.4.1

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.4.0

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.3.1

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.3.0

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.2.2

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.2.1

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.2.0

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.1.1

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.1.0

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.0.3

2 findings

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: harpsealjs → hardfist (on 2025-01-25) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2025-01-25. This could indicate a legitimate maintainer transition or an account compromise.

v1.0.2

2 findings

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: harpsealjs → hardfist (on 2025-01-23) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2025-01-23. This could indicate a legitimate maintainer transition or an account compromise.

v1.0.1

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.0.0

2 findings

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: hardfist → harpsealjs (on 2024-08-10) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2024-08-10. This could indicate a legitimate maintainer transition or an account compromise.

v0.7.5

1 finding

INFO No provenance attestation provenance

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

v0.7.4

1 finding

INFO No provenance attestation provenance

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

v0.7.3

1 finding

INFO No provenance attestation provenance

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

v0.7.2

1 finding

INFO No provenance attestation provenance

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

v0.7.1

1 finding

INFO No provenance attestation provenance

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

v0.7.0

1 finding

INFO No provenance attestation provenance

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

v0.6.5

1 finding

INFO No provenance attestation provenance

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

v0.6.4

1 finding

INFO No provenance attestation provenance

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

v0.6.3

1 finding

INFO No provenance attestation provenance

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

v0.3.3

2 findings

HIGH Low-value / spam package indicators (4 signals, score 8) bogus-package

Matched 4 signal(s), weighted score 8: • [S_PUBLISHER_MASS_PRODUCTION] Maintainer 'iwanabethatguy' owns 27 packages, ≥70% share a templated name shape. • [S_README_LINKDUMP] README is a link dump (5 URLs) that barely mentions the package — typical of phishing link farms. • [S_README_NO_CODE] Short README with no code block, no install instructions, and no usage/API section. • [S_NO_KEYWORDS] No keywords declared.

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.