@exodus/react-native-screenshot-detector
detect when the user takes a screenshot
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Long-stable publisher change from 2021, org-style maintainer list, no malicious diff. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with historical org maintainer rotation, not a takeover. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Change is old and stable (1929d), explicitly noted as inconsistent with takeover. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.2.7 | 0 / 0 | |
| 1.2.6 | 0 / 0 | |
| 1.2.5 | 0 / 0 | |
| 1.2.4 | 0 / 0 | |
| 1.2.3 | 0 / 0 | |
| 1.2.2 | 0 / 0 | |
| 1.2.1 | 0 / 0 | |
| 1.2.0 | 0 / 0 | |
| 1.1.2 | 0 / 0 | |
| 1.1.1 | 0 / 0 | |
| 1.1.0 | 0 / 0 | |
| 1.0.1 | 0 / 0 | |
| 1.0.0 | 0 / 0 |
v1.1.2
2 findingsThis version was published by a different npm account (alex.alexandrius) than the most recent previously approved version (tenaciousmv) on 2023-01-05. It has since remained available on npm for 1297 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
2 findingsThis version was published by a different npm account (andrejb) than the most recent previously approved version (tenaciousmv) on 2021-04-14. It has since remained available on npm for 1928 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findingsThis version was published by a different npm account (andrejb) than the most recent previously approved version (tenaciousmv) on 2021-04-13. It has since remained available on npm for 1929 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.