@powersync/react
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.10.0 | 0 / 13 | |
| 1.9.1 | 0 / 13 | |
| 1.9.0 | 0 / 13 | |
| 1.8.3 | 0 / 13 | |
| 1.8.2 | 0 / 10 | |
| 1.8.1 | 0 / 10 | |
| 1.8.0 | 0 / 10 | |
| 1.7.4 | 0 / 10 | |
| 1.7.3 | 0 / 10 | |
| 1.7.2 | 0 / 10 | |
| 1.7.1 | 0 / 9 | |
| 1.7.0 | 0 / 9 | |
| 1.6.0 | 0 / 9 |
v1.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.