← Home

@expo/spawn-async

npm Repository Homepage

A Promise-based interface into processes created by child_process.spawn

10
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

idebrentvatneevanbaconexpoadminexponentbycedrickudochienalanhughestsapetaexpo-botphilplwschurman

Keywords

spawnchild_processasyncpromiseprocess

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from dsokal to ide is an internal Expo team rotation; both are established Expo maintainers. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers are Expo team members; normal org roster changes. ai
maintainer-change maintainer-removed AI (maintainer-change): Removed maintainers reflect normal Expo team roster changes. ai

Versions (showing 10 of 10)

Version Deps Published
1.8.0 1 / 6
1.7.2 1 / 6
1.7.1 1 / 6
1.7.0 1 / 6
1.6.0 1 / 6
1.5.0 1 / 5
1.4.2 1 / 5
1.4.0 2 / 4
1.3.0 1 / 5
1.2.8 1 / 5

v1.8.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: ide → philpl (on 2026-05-19) provenance

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

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

2 findings
HIGH Publisher changed: dsokal → ide (on 2022-07-27) provenance

This version was published by a different npm account than previous versions on 2022-07-27. 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.

v1.6.0

2 findings
HIGH Publisher changed: fson → dsokal (on 2022-01-27) provenance

This version was published by a different npm account than previous versions on 2022-01-27. 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.

v1.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: dsokal → fson (on 2019-05-30) provenance

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

v1.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: ide → dsokal (on 2019-04-19) provenance

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.8

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.