@expo/expo-modules-macros-plugin
Swift macro plugin for Expo modules
2
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): Swift macro plugins require a compiled binary tool; ExpoModulesMacros-tool is the expected artifact for this package's purpose as a Swift macro plugin for Expo modules. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): philpl is a known Expo/React Native contributor; addition is consistent with legitimate team management at 650 Industries for an official @expo/ scoped package. | ai |
v0.0.8
2 findings
HIGH
Bundled binary files (1)
npm-metadata
Package contains compiled binaries that could be backdoors: • apple/ExpoModulesMacros-tool
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
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.