react-native-qrcode-svg
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Vetted transition to expensify (98/0 track record); stable across future versions. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same legit expensify transfer; not a compromise. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 6.3.21 | 3 / 10 | |
| 6.3.20 | 3 / 10 | |
| 6.3.19 | 3 / 10 | |
| 6.3.16 | 3 / 10 | |
| 6.3.15 | 3 / 10 | |
| 6.3.14 | 3 / 10 | |
| 6.3.12 | 3 / 10 | |
| 6.3.11 | 3 / 10 | |
| 6.3.2 | 3 / 9 | |
| 6.3.1 | 2 / 9 | |
| 6.3.0 | 2 / 9 | |
| 6.2.0 | 2 / 9 | |
| 6.1.2 | 2 / 9 | |
| 6.1.1 | 2 / 9 | |
| 6.1.0 | 2 / 9 | |
| 6.0.7 | 2 / 9 | |
| 6.0.6 | 2 / 9 | |
| 6.0.5 | 2 / 10 | |
| 6.0.3 | 2 / 10 | |
| 6.0.1 | 2 / 10 | |
| 6.0.0 | 2 / 10 |
v6.3.15
2 findingsThis version was published by a different npm account than previous versions on 2025-02-21. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.3.14
2 findingsThis version was published by a different npm account than previous versions on 2025-01-08. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.12
2 findingsThis version was published by a different npm account than previous versions on 2024-10-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.11
2 findingsThis version was published by a different npm account than previous versions on 2024-10-15. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.