react-native-safe-area-view

Add padding to your views to account for notches, home indicators, status bar, and possibly other future things.

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

brentvatnedavepacksatya164

Keywords

react-nativeiPhoneXSafeAreaViewsafe areanotch

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): brentvatne is a co-author listed in package.json and a well-known React Native/Expo core contributor. The transition from satya164 is a legitimate maintainer handoff.	ai	2026/04/24
source-diff	obfuscated-file:lib/commonjs/index.js	AI (source-diff): Standard Babel/bob-compiled CommonJS output. Code is readable React Native component logic; long lines are a build artifact, not obfuscation.	ai	2026/04/24
source-diff	obfuscated-file:lib/module/index.js	AI (source-diff): Standard Babel/bob-compiled ESM output. Code is readable React Native component logic; long lines are a build artifact, not obfuscation.	ai	2026/04/24

Versions (showing 29 of 29)

Version	Deps	Published
2.0.0	1 / 9	2020-05-15
1.1.1	1 / 9	2020-04-25
1.1.0	1 / 9	2020-04-19
1.0.0	1 / 9	2019-09-26
0.14.9	1 / 2	2020-04-07
0.14.8	1 / 2	2019-09-06
0.14.7	1 / 2	2019-08-10
0.14.6	1 / 2	2019-07-03
0.14.5	1 / 2	2019-06-06
0.14.4	1 / 2	2019-05-20
0.14.3	1 / 2	2019-05-16
0.14.2	1 / 2	2019-05-16
0.14.1	1 / 2	2019-05-10
0.14.0	1 / 2	2019-05-10
0.13.2	1 / 2	2019-05-09
0.13.1	1 / 2	2019-02-27
0.13.0	1 / 2	2019-02-25
0.12.0	1 / 2	2019-01-09
0.11.0	1 / 2	2018-09-19
0.10.0	1 / 2	2018-09-07
0.9.0	1 / 2	2018-06-11
0.8.0	1 / 2	2018-05-25
0.7.0	1 / 2	2018-02-19
0.6.0	1 / 2	2018-02-07
0.5.0	1 / 0	2018-02-05
0.4.0	1 / 0	2018-01-25
0.3.0	1 / 0	2018-01-20
0.2.0	1 / 0	2017-11-21
0.1.0	3 / 0	2017-10-31

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

4 findings

HIGH Publisher changed: satya164 → brentvatne (on 2020-04-19) provenance

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

HIGH New obfuscated file: lib/commonjs/index.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: lib/module/index.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.0.0

3 findings

HIGH New obfuscated file: lib/commonjs/index.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: lib/module/index.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.14.9

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: brentvatne → satya164 (on 2020-04-07) provenance

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

v0.14.8

1 finding

LOW No provenance attestation provenance

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

v0.14.7

1 finding

LOW No provenance attestation provenance

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

v0.14.6

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: brentvatne → satya164 (on 2019-07-03) provenance

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

v0.14.5

1 finding

LOW No provenance attestation provenance

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

v0.14.4

1 finding

LOW No provenance attestation provenance

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

v0.14.3

1 finding

LOW No provenance attestation provenance

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

v0.14.2

1 finding

LOW No provenance attestation provenance

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

v0.14.1

1 finding

LOW No provenance attestation provenance

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

v0.14.0

1 finding

LOW No provenance attestation provenance

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

v0.13.2

1 finding

LOW No provenance attestation provenance

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

v0.13.1

1 finding

LOW No provenance attestation provenance

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

v0.13.0

1 finding

LOW No provenance attestation provenance

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

v0.12.0

1 finding

LOW No provenance attestation provenance

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

v0.11.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: davepack → brentvatne (on 2018-09-19) provenance

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

v0.10.0

1 finding

LOW No provenance attestation provenance

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

v0.9.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: brentvatne → davepack (on 2018-06-11) provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.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: davepack → brentvatne (on 2018-02-19) provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

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