← Home

@react-native-community/art

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

ansal_alibartolkaruzacharpeniconnectdotzcpojerdmtr.kovalenkoempyricalesemesekferrannpgrabboujanicduplessisjohandutoitkelsetkrizzuluancurtimattoakesmike.nedosekinmike866mmazzarolomsandnaturalclarnicholaslee119pvinisrafaellpareact-native-community-botrewieersafaiyehsatya164scott.becaswaagiethymikeetitozzztrensikvonovakwojteg1337

Keywords

react-nativereact nativereact-native-artreact-native-communityart

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:got AI (typosquat): Scoped community package; Levenshtein match against 'got' is a false positive. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): Scoped community package; Levenshtein match against 'ajv' is a false positive. ai

Versions (showing 1 of 1)

Version Deps Published
1.2.0 3 / 9

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