@quiltt/react-native
React Native Components for Quiltt Connector
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established publisher with 16 approved packages; provenance absence is a process gap, not a security signal for this package. | ai | |
| phantom-deps | phantom-dep:lodash.debounce | AI (phantom-deps): lodash.debounce is a declared runtime dep in this package; phantom-dep is a false positive here. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 6.0.0 | 5 / 13 | |
| 5.3.0 | 5 / 13 | |
| 5.2.5 | 5 / 13 | |
| 5.2.4 | 5 / 13 | |
| 5.2.3 | 5 / 13 | |
| 5.2.2 | 5 / 13 | |
| 5.2.0 | 5 / 13 | |
| 5.1.3 | 5 / 13 | |
| 5.1.2 | 5 / 13 | |
| 5.1.1 | 5 / 13 | |
| 5.1.0 | 5 / 13 | |
| 5.0.3 | 5 / 13 | |
| 5.0.2 | 5 / 13 | |
| 5.0.1 | 5 / 13 | |
| 5.0.0 | 5 / 13 | |
| 4.5.1 | 4 / 14 | |
| 4.5.0 | 4 / 13 | |
| 4.4.0 | 4 / 13 | |
| 4.3.3 | 4 / 13 |
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.