@powersync/common
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index.d.cts | AI (source-diff): Bundled TypeScript declaration file (.d.cts) for CJS exports; long lines are normal for rollup-generated type bundles. | ai |
Versions (showing 51 of 74)
| Version | Deps | Published |
|---|---|---|
| 2.0.0 | 0 / 3 | |
| 1.57.2 | 1 / 15 | |
| 1.57.1 | 1 / 15 | |
| 1.57.0 | 1 / 15 | |
| 1.56.0 | 1 / 15 | |
| 1.55.0 | 1 / 15 | |
| 1.54.0 | 2 / 15 | |
| 1.53.2 | 2 / 14 | |
| 1.53.1 | 2 / 14 | |
| 1.53.0 | 2 / 14 | |
| 1.52.0 | 1 / 16 | |
| 1.51.0 | 1 / 14 | |
| 1.50.0 | 1 / 14 | |
| 1.49.0 | 2 / 14 | |
| 1.48.0 | 2 / 14 | |
| 1.47.0 | 2 / 14 | |
| 1.46.0 | 2 / 14 | |
| 1.45.0 | 2 / 13 | |
| 1.44.0 | 2 / 13 | |
| 1.43.1 | 2 / 13 | |
| 1.43.0 | 2 / 13 | |
| 1.42.0 | 3 / 12 | |
| 1.41.1 | 3 / 12 | |
| 1.41.0 | 1 / 17 | |
| 1.40.0 | 1 / 17 | |
| 1.39.0 | 1 / 17 | |
| 1.38.1 | 1 / 17 | |
| 1.38.0 | 1 / 17 | |
| 1.37.0 | 1 / 17 | |
| 1.36.0 | 1 / 17 | |
| 1.35.0 | 1 / 17 | |
| 1.34.0 | 1 / 17 | |
| 1.33.2 | 1 / 17 | |
| 1.33.1 | 1 / 17 | |
| 1.33.0 | 1 / 17 | |
| 1.32.0 | 1 / 18 | |
| 1.31.1 | 1 / 18 | |
| 1.31.0 | 1 / 18 | |
| 1.30.0 | 1 / 18 | |
| 1.29.0 | 1 / 18 | |
| 1.28.0 | 1 / 18 | |
| 1.27.1 | 1 / 18 | |
| 1.27.0 | 1 / 18 | |
| 1.26.0 | 1 / 18 | |
| 1.25.0 | 1 / 18 | |
| 1.24.0 | 1 / 20 | |
| 1.23.0 | 1 / 20 | |
| 1.22.2 | 1 / 20 | |
| 1.22.1 | 1 / 20 | |
| 1.22.0 | 1 / 20 | |
| 1.21.0 | 1 / 20 |
v2.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.57.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.57.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.51.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.50.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.49.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.48.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.47.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (journeyapps-platform) on 2026-02-16, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v1.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.43.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
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.0
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.