@xtaskjs/cqrs
CQRS integration for xtaskjs with read/write datasource bindings.
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:cors | AI (typosquat): CQRS is a legitimate architectural pattern name; scoped package @xtaskjs/cqrs is not impersonating cors. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): 2-edit distance to qs is coincidental; package is clearly a CQRS module in the xtaskjs ecosystem. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.1.14 | 2 / 10 | |
| 1.1.10 | 2 / 10 | |
| 1.1.8 | 2 / 10 | |
| 1.1.7 | 2 / 10 | |
| 1.1.6 | 2 / 10 | |
| 1.1.5 | 2 / 10 | |
| 1.1.4 | 2 / 10 | |
| 1.1.3 | 2 / 10 | |
| 1.1.2 | 2 / 10 | |
| 1.1.1 | 2 / 10 |
v1.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
2 findingsPackage name '@xtaskjs/cqrs' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
2 findingsPackage name '@xtaskjs/cqrs' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
2 findingsPackage name '@xtaskjs/cqrs' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
2 findingsPackage name '@xtaskjs/cqrs' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
2 findingsPackage name '@xtaskjs/cqrs' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
2 findingsPackage name '@xtaskjs/cqrs' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
2 findingsPackage name '@xtaskjs/cqrs' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
2 findingsPackage name '@xtaskjs/cqrs' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.