← Home

@exodus/react-native-fs

npm Repository Homepage

Native filesystem access for react-native

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

Maintainers

juraexkevvadoguhanjanweyevhenii_molodykjaviexodusismamzexojoferi42jprichardsonfarisissaryanzimheadfiregutenyemosesbotroccomusodcastagnolisonayevestenaciousmvasyakostbulgakovkchalkerandrejbjaydp17olisticjoepie91merlzvboninimol0dverohellodevopsrobotjenish-sojitraantohellomarkoexodusnachoalvarezgiovannircofilipexoduscryptosgrandrescarreondiegomuralanre-markguillecuramariosvladfederico-poakinncarfboucquezlanahizzlekwwoodumitojoshuabotiaacekmeniemskapalaawilson-rsggabarrin-rsralph.badanh.t.vovoltagebotsryansquared-npmalexandrbbmsergii_boflorianmathieurgommezzangellozexodus-justin.zaalex.alexandriusrecrg911jamiemawjames-greshehryar6geoffreyroussetclarkexotunguyennnnnjschopencawfreemarcos.kichelandrewtoth-exoduscdotta-exodusexorichmmehta-10kryptkeep633kh4ckmbaraniak-exodusjeehahnhasakuraawesomenikodavidexodusr4vnnantoaquiexoleoale-exofrankliexodusbekatdronaldcrbmuratsoguillermo_hhcc-exodusyalomistjoshua-rogers-exodusjdmdreamervikas027angel_exodussripwoudcoreycollinsxogdgchrisrichexoharshjvjosuexogarana-exoduskuchoksaravanan7manishailendrakumaromkarjosemiguelherreraweb3yevhenii-mo-exodusbewardensamuelscheit1emuandyespdj_exodus

Keywords

react-componentreact-nativeiosandroidfsfilesystemdownloaduploadfile-transfer

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Stale 2020 transfer, long-stable on npm, not a fresh takeover signal. ai
maintainer-change maintainer-removed AI (maintainer-change): Same stale historical transfer as maintainer-added. ai
provenance publisher-changed-stale AI (provenance): 2203 days stable, explicitly flagged by analyzer as inconsistent with takeover. ai

Versions (showing 11 of 11)

Version Deps Published
2.23.0 0 / 6
2.22.0 2 / 6
2.21.0 2 / 6
2.20.0 2 / 6
2.19.0 2 / 6
2.18.0 2 / 6
2.17.0 2 / 6
2.16.0 2 / 6
2.15.0 2 / 6
2.14.2 2 / 6
2.14.1 2 / 6

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

v2.21.0

2 findings
MEDIUM Publisher changed: andrejb → ariene-exodus (on 2022-04-18, unremoved on npm for 1559d) provenance

This version was published by a different npm account (ariene-exodus) than the most recent previously approved version (andrejb) on 2022-04-18. It has since remained available on npm for 1559 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.

v2.20.0

1 finding
LOW No provenance attestation provenance

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

v2.19.0

1 finding
LOW No provenance attestation provenance

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

v2.18.0

1 finding
LOW No provenance attestation provenance

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

v2.17.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: tenaciousmv → andrejb (on 2021-03-02, known maintainer) provenance

This version was published by a different npm account (andrejb) than the most recent previously approved version (tenaciousmv) on 2021-03-02, but andrejb is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.16.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: sonaye → tenaciousmv (on 2021-02-22, known maintainer) provenance

This version was published by a different npm account (tenaciousmv) than the most recent previously approved version (sonaye) on 2021-02-22, but tenaciousmv is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.15.0

2 findings
MEDIUM Publisher changed: sonaye → andrejb (on 2020-07-13, unremoved on npm for 2203d) provenance

This version was published by a different npm account (andrejb) than the most recent previously approved version (sonaye) on 2020-07-13. It has since remained available on npm for 2203 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.

v2.14.2

1 finding
LOW No provenance attestation provenance

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

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