@react-native-community/push-notification-ios

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

thymikeenaturalclar

Keywords

react-nativereact nativepush notification iospush notificationnotification iosnotification

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): Publish-env change under trusted maintainer; no payload change.	ai	2026/07/22
maintainer-change	maintainer-added	AI (maintainer-change): Legitimate 2019 handoff to react-native-community; stable.	ai	2026/07/22
provenance	publisher-changed-stale	AI (provenance): Old, long-lived transfer to community org; not a takeover.	ai	2026/07/22

Versions (showing 30 of 30)

Version	Deps	Published
1.12.0	1 / 11	2025-12-16
1.11.0	1 / 11	2023-04-05
1.10.1	1 / 11	2021-09-08
1.10.0	1 / 11	2021-08-20
1.9.0	1 / 11	2021-08-10
1.8.0	1 / 12	2020-11-25
1.7.4	1 / 12	2020-11-22
1.7.3	1 / 12	2020-11-09
1.7.2	1 / 12	2020-11-09
1.7.1	1 / 12	2020-10-26
1.7.0	1 / 12	2020-10-26
1.6.1	1 / 12	2020-10-19
1.6.0	1 / 12	2020-10-13
1.5.0	1 / 12	2020-09-12
1.4.1	1 / 12	2020-08-19
1.4.0	1 / 12	2020-07-21
1.3.0	1 / 12	2020-07-04
1.2.2	1 / 12	2020-06-08
1.2.1	1 / 12	2020-06-08
1.2.0	1 / 12	2020-05-02
1.1.1	1 / 13	2020-04-01
1.1.0	1 / 13	2020-03-19
1.0.7	1 / 14	2020-02-28
1.0.6	1 / 14	2020-02-11
1.0.5	1 / 14	2020-01-11
1.0.4	1 / 14	2020-01-09
1.0.3	1 / 9	2019-11-12
1.0.2	1 / 9	2019-07-30
1.0.1	1 / 9	2019-03-01
1.0.0	1 / 9	2019-02-12

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

1 finding

LOW No provenance attestation provenance

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

v1.10.1

1 finding

LOW No provenance attestation provenance

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

v1.10.0

1 finding

LOW No provenance attestation provenance

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

v1.9.0

1 finding

LOW No provenance attestation provenance

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

v1.8.0

1 finding

LOW No provenance attestation provenance

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

v1.7.4

1 finding

LOW No provenance attestation provenance

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

v1.7.3

1 finding

LOW No provenance attestation provenance

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

v1.7.2

1 finding

LOW No provenance attestation provenance

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

v1.7.1

1 finding

LOW No provenance attestation provenance

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

v1.7.0

1 finding

LOW No provenance attestation provenance

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

v1.6.1

1 finding

LOW No provenance attestation provenance

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

v1.6.0

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

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

1 finding

LOW No provenance attestation provenance

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

v1.2.2

1 finding

LOW No provenance attestation provenance

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

v1.2.1

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.1

1 finding

LOW No provenance attestation provenance

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

v1.1.0

1 finding

LOW No provenance attestation provenance

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

v1.0.7

2 findings

MEDIUM Publisher changed: rafaellpa → naturalclar (on 2020-02-28, unremoved on npm for 2335d) provenance

This version was published by a different npm account (naturalclar) than the most recent previously approved version (rafaellpa) on 2020-02-28. It has since remained available on npm for 2335 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.0.6

2 findings

MEDIUM Publisher changed: rafaellpa → naturalclar (on 2020-02-11, unremoved on npm for 2353d) provenance

This version was published by a different npm account (naturalclar) than the most recent previously approved version (rafaellpa) on 2020-02-11. It has since remained available on npm for 2353 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.0.5

3 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: naturalclar.

MEDIUM Publisher changed: rafaellpa → naturalclar (on 2020-01-11, unremoved on npm for 2383d) provenance

This version was published by a different npm account (naturalclar) than the most recent previously approved version (rafaellpa) on 2020-01-11. It has since remained available on npm for 2383 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.0.4

3 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: thymikee.

MEDIUM Publisher changed: rafaellpa → thymikee (on 2020-01-09, unremoved on npm for 2385d) provenance

This version was published by a different npm account (thymikee) than the most recent previously approved version (rafaellpa) on 2020-01-09. It has since remained available on npm for 2385 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.0.3

3 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: thymikee.

MEDIUM Publisher changed: rafaellpa → thymikee (on 2019-11-12, unremoved on npm for 2443d) provenance

This version was published by a different npm account (thymikee) than the most recent previously approved version (rafaellpa) on 2019-11-12. It has since remained available on npm for 2443 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.0.2

3 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: thymikee.

MEDIUM Publisher changed: rafaellpa → thymikee (on 2019-07-30, unremoved on npm for 2549d) provenance

This version was published by a different npm account (thymikee) than the most recent previously approved version (rafaellpa) on 2019-07-30. It has since remained available on npm for 2549 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

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