@loadable/component MIT 34 versions

@loadable/component

npm Repository Homepage

React code splitting made easy.

34

Versions

MIT

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

neozirokashey

Keywords

reactssrwebpackcode-splittingreact-routerserver-side-renderingdynamic-importreact-loadablereact-async-components

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Documented maintainer transition from neoziro to kashey for the loadable-components project. kashey has a strong track record (530 approved packages). Legitimate handoff, not a compromise.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): Same maintainer transition event — kashey is a trusted, long-standing npm publisher. Stable accept for this package.	ai	2026/04/24
publish-pattern	new-deps-added	AI (publish-pattern): react-is is an official React team package, widely trusted. Its addition is consistent with @loadable/component's React SSR use case.	ai	2026/04/24

Versions (showing 34 of 34)

Version	Deps	Published
5.16.7	3 / 0	2025-05-18
5.16.4	3 / 0	2024-04-20
5.16.3	3 / 0	2023-12-26
5.16.2	3 / 0	2023-12-15
5.15.3	3 / 0	2023-01-28
5.15.2	3 / 0	2021-12-12
5.15.0	3 / 0	2021-05-08
5.14.1	3 / 0	2020-10-22
5.14.0	3 / 0	2020-10-20
5.13.2	3 / 0	2020-09-14
5.13.1	3 / 0	2020-07-02
5.13.0	3 / 0	2020-06-29
5.12.0	2 / 0	2020-01-09
5.11.0	2 / 0	2019-12-02
5.10.3	2 / 0	2019-09-24
5.10.2	2 / 0	2019-07-15
5.10.1	2 / 0	2019-05-14
5.10.0	2 / 0	2019-05-13
5.9.0	1 / 0	2019-04-23
5.7.0	1 / 0	2019-03-14
5.6.1	1 / 0	2019-02-25
5.6.0	1 / 0	2019-02-05
5.5.0	1 / 0	2019-01-22
5.2.2	1 / 0	2018-12-12
5.2.1	1 / 0	2018-11-27
5.1.2	1 / 0	2018-11-13
5.0.1	1 / 0	2018-11-10
5.0.0	1 / 0	2018-11-10
4.0.2	1 / 0	2018-10-31
4.0.1	1 / 0	2018-10-30
4.0.0	1 / 0	2018-10-30
3.0.2	1 / 0	2018-10-30
3.0.1	1 / 0	2018-10-30
3.0.0	1 / 0	2018-10-29

v5.16.7

1 finding

LOW No provenance attestation provenance

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

v5.16.4

1 finding

LOW No provenance attestation provenance

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

v5.16.3

1 finding

LOW No provenance attestation provenance

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

v5.16.2

1 finding

LOW No provenance attestation provenance

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

v5.15.3

1 finding

LOW No provenance attestation provenance

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

v5.15.2

1 finding

LOW No provenance attestation provenance

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

v5.15.0

1 finding

LOW No provenance attestation provenance

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

v5.14.1

1 finding

LOW No provenance attestation provenance

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

v5.14.0

1 finding

LOW No provenance attestation provenance

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

v5.13.2

2 findings

HIGH Publisher changed: neoziro → kashey (on 2020-09-14) provenance

This version was published by a different npm account than previous versions on 2020-09-14. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v5.13.1

2 findings

HIGH Publisher changed: neoziro → kashey (on 2020-07-02) provenance

This version was published by a different npm account than previous versions on 2020-07-02. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v5.13.0

2 findings

HIGH Publisher changed: neoziro → kashey (on 2020-06-29) provenance

This version was published by a different npm account than previous versions on 2020-06-29. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v5.12.0

1 finding

LOW No provenance attestation provenance

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

v5.11.0

1 finding

LOW No provenance attestation provenance

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

v5.10.3

1 finding

LOW No provenance attestation provenance

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

v5.10.2

1 finding

LOW No provenance attestation provenance

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

v5.10.1

1 finding

LOW No provenance attestation provenance

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

v5.10.0

1 finding

LOW No provenance attestation provenance

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

v5.9.0

1 finding

LOW No provenance attestation provenance

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

v5.7.0

1 finding

LOW No provenance attestation provenance

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

v5.6.1

1 finding

LOW No provenance attestation provenance

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

v5.6.0

1 finding

LOW No provenance attestation provenance

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

v5.5.0

1 finding

LOW No provenance attestation provenance

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

v5.2.2

1 finding

LOW No provenance attestation provenance

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

v5.2.1

1 finding

LOW No provenance attestation provenance

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

v5.1.2

1 finding

LOW No provenance attestation provenance

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

v5.0.1

1 finding

LOW No provenance attestation provenance

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

v5.0.0

1 finding

LOW No provenance attestation provenance

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

v4.0.2

1 finding

LOW No provenance attestation provenance

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

v4.0.1

1 finding

LOW No provenance attestation provenance

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

v4.0.0

1 finding

LOW No provenance attestation provenance

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