@wordpress/sync
Sync Data.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:import-locals | AI (phantom-deps): Used in config files only, not directly imported; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@types/simple-peer | AI (phantom-deps): Type-only dependency loaded by convention; not a runtime concern. | ai | |
| typosquat | typosquat.levenshtein:async | AI (typosquat): Legitimate WordPress/Gutenberg package; name similarity to 'async' is coincidental, not impersonation. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.48.0 | 9 / 2 | |
| 1.47.0 | 9 / 2 | |
| 1.46.0 | 9 / 2 | |
| 1.45.0 | 9 / 2 | |
| 1.44.0 | 9 / 2 | |
| 1.43.0 | 9 / 2 | |
| 1.42.0 | 9 / 2 | |
| 1.41.0 | 9 / 2 | |
| 1.40.0 | 9 / 2 | |
| 1.39.0 | 7 / 3 | |
| 1.38.0 | 9 / 1 | |
| 1.35.0 | 10 / 0 | |
| 1.34.0 | 10 / 0 | |
| 1.33.1 | 10 / 0 | |
| 1.32.0 | 10 / 0 | |
| 1.31.0 | 10 / 0 | |
| 1.30.0 | 10 / 0 | |
| 1.24.0 | 10 / 0 |
v1.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.