@powersync/react-native
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Active monorepo package with 212 versions and SLSA provenance; dormancy flag is a false positive for this release cadence. | ai | |
| dependencies | unvetted-dep:@powersync/react | AI (dependencies): Sibling package in the same powersync-ja monorepo; not a third-party risk. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.35.2 | 2 / 16 | |
| 1.35.1 | 2 / 16 | |
| 1.35.0 | 2 / 16 | |
| 1.34.0 | 2 / 17 | |
| 1.26.0 | 2 / 18 | |
| 1.25.1 | 2 / 18 | |
| 1.25.0 | 2 / 18 | |
| 1.24.3 | 2 / 18 | |
| 1.24.2 | 2 / 18 | |
| 1.24.1 | 2 / 18 | |
| 1.24.0 | 2 / 18 | |
| 1.23.2 | 2 / 18 | |
| 1.23.1 | 2 / 18 | |
| 1.23.0 | 2 / 18 | |
| 1.22.2 | 2 / 18 | |
| 1.22.1 | 2 / 18 | |
| 1.22.0 | 2 / 18 | |
| 1.21.0 | 2 / 18 | |
| 1.20.4 | 2 / 18 | |
| 1.20.3 | 2 / 18 | |
| 1.20.2 | 2 / 18 |
v1.35.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.35.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.35.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.34.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.