@fraym/sync
JS client implementation of the sync service of Fr[ae]ym
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:async | AI (typosquat): Scoped @fraym org package; 'sync' describes gRPC sync service, not a typosquat of 'async'. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 1.1.0 | 3 / 0 | |
| 1.0.27 | 3 / 0 | |
| 1.0.26 | 3 / 0 | |
| 1.0.25 | 3 / 0 | |
| 1.0.24 | 3 / 0 | |
| 1.0.23 | 3 / 0 | |
| 1.0.22 | 3 / 0 | |
| 1.0.21 | 3 / 0 | |
| 1.0.20 | 3 / 0 | |
| 1.0.19 | 3 / 0 | |
| 1.0.18 | 3 / 0 | |
| 1.0.17 | 3 / 0 | |
| 1.0.16 | 3 / 0 | |
| 1.0.15 | 3 / 0 | |
| 1.0.13 | 3 / 0 | |
| 1.0.11 | 3 / 0 | |
| 1.0.10 | 3 / 0 | |
| 1.0.9 | 3 / 0 | |
| 1.0.8 | 3 / 0 | |
| 1.0.7 | 3 / 0 | |
| 1.0.6 | 3 / 0 | |
| 1.0.5 | 3 / 0 | |
| 1.0.4 | 3 / 0 | |
| 1.0.3 | 3 / 0 | |
| 1.0.2 | 3 / 0 | |
| 1.0.1 | 3 / 0 | |
| 1.0.0 | 3 / 0 | |
| 0.50.3 | 3 / 0 | |
| 0.50.2 | 3 / 0 | |
| 0.50.1 | 3 / 0 | |
| 0.50.0 | 3 / 0 | |
| 0.49.7 | 3 / 0 | |
| 0.49.6 | 3 / 0 | |
| 0.49.5 | 3 / 0 |
v1.0.27
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.26
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.25
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.24
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.23
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.22
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.21
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.20
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.19
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.18
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.17
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.16
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.15
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.13
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.50.3
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.50.2
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.50.1
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.50.0
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.49.7
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.49.6
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.49.5
2 findingsPackage name '@fraym/sync' is 1 edit(s) away from popular package 'async'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.