@quiltt/capacitor
Capacitor plugin 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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@quiltt/react | AI (dependencies): First-party Quiltt monorepo package, version-locked to match this package's own release. | ai | |
| dependencies | unvetted-dep:@quiltt/vue | AI (dependencies): First-party Quiltt monorepo package, version-locked to match this package's own release. | ai | |
| provenance | no-provenance | AI (provenance): Quiltt org packages consistently lack Sigstore provenance; not a risk signal for this publisher. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 6.0.1 | 2 / 13 | |
| 6.0.0 | 2 / 13 | |
| 5.3.0 | 2 / 13 | |
| 5.2.5 | 2 / 13 | |
| 5.2.4 | 2 / 13 | |
| 5.2.3 | 2 / 13 | |
| 5.2.2 | 2 / 13 | |
| 5.2.0 | 2 / 13 | |
| 5.1.3 | 0 / 15 | |
| 5.1.2 | 0 / 15 |
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 finding[Accepted risk] Package 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.