react-addons-create-fragment MIT 28 versions

react-addons-create-fragment

npm Repository Homepage

28

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

sophiebitstrueadmgaearonbrianvaughnfb

Keywords

reactreact-addon

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): sophiebits (Sophie Alpert) is a well-known React core team member; the gaearon→sophiebits transition in 2017 was a legitimate Facebook/React team publishing consolidation.	ai	2026/04/23
maintainer-change	maintainer-added	AI (maintainer-change): sophiebits is a long-standing React core team member with a strong track record; addition is part of legitimate React team publishing consolidation.	ai	2026/04/23
maintainer-change	maintainer-removed	AI (maintainer-change): Removal of previous React team maintainers is part of the documented 2017 React npm publishing consolidation, not a hostile takeover.	ai	2026/04/23
bogus-package	bogus-package	AI (bogus-package): fb and gaearon are official Facebook/React maintainers, not spam publishers. No-description is typical for React addon shim packages.	ai	2026/04/23
phantom-deps	phantom-dep:loose-envify	AI (phantom-deps): loose-envify is used as a browserify transform (declared in browserify config), not a direct import — standard pattern for React addon packages.	ai	2026/04/23
phantom-deps	phantom-dep:object-assign	AI (phantom-deps): object-assign is used in the build/bundle process for this React addon; phantom-dep flag is a false positive for this package's build pattern.	ai	2026/04/23

Versions (showing 28 of 28)

Version	Deps	Published
15.6.2	3 / 4	2017-09-26
15.6.0	3 / 4	2017-06-14
15.5.4	3 / 3	2017-05-09
15.5.3	2 / 3	2017-04-09
15.5.2	2 / 3	2017-04-07
15.5.1	2 / 3	2017-04-02
15.5.0	2 / 3	2017-03-31
15.4.2	2 / 0	2017-01-06
15.4.1	0 / 0	2016-11-23
15.4.0	0 / 0	2016-11-16
15.3.2	0 / 0	2016-09-19
15.3.1	0 / 0	2016-08-19
15.3.0	0 / 0	2016-07-29
15.2.1	0 / 0	2016-07-08
15.2.0	0 / 0	2016-07-01
15.1.0	0 / 0	2016-05-20
15.0.2	0 / 0	2016-04-30
15.0.1	0 / 0	2016-04-08
15.0.0	0 / 0	2016-04-07
0.14.8	0 / 0	2016-03-29
0.14.7	0 / 0	2016-01-28
0.14.6	0 / 0	2016-01-06
0.14.5	0 / 0	2015-12-29
0.14.4	0 / 0	2015-12-29
0.14.3	0 / 0	2015-11-19
0.14.2	0 / 0	2015-11-02
0.14.1	0 / 0	2015-10-28
0.14.0	0 / 0	2015-10-07

v15.6.2

2 findings

HIGH Publisher changed: gaearon → sophiebits (on 2017-09-26) provenance

This version was published by a different npm account than previous versions on 2017-09-26. 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.

v15.6.0

1 finding

LOW No provenance attestation provenance

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

v15.5.4

1 finding

LOW No provenance attestation provenance

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

v15.5.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: brianvaughn → gaearon (on 2017-04-09) provenance

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

v15.5.2

1 finding

LOW No provenance attestation provenance

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

v15.5.1

1 finding

LOW No provenance attestation provenance

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

v15.5.0

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: gaearon → brianvaughn (on 2017-03-31) provenance

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

v15.4.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: spicyj → gaearon (on 2017-01-06) provenance

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

v15.4.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: tomocchino → spicyj (on 2016-11-23) provenance

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

v15.4.0

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: zpao → tomocchino (on 2016-11-16) provenance

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

v15.3.2

1 finding

LOW No provenance attestation provenance

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

v15.3.1

1 finding

LOW No provenance attestation provenance

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

v15.3.0

1 finding

LOW No provenance attestation provenance

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

v15.2.1

1 finding

LOW No provenance attestation provenance

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

v15.2.0

1 finding

LOW No provenance attestation provenance

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

v15.1.0

1 finding

LOW No provenance attestation provenance

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

v15.0.2

1 finding

LOW No provenance attestation provenance

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

v15.0.1

1 finding

LOW No provenance attestation provenance

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

v15.0.0

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: gaearon → zpao (on 2016-04-07) provenance

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