@jay-framework/wix-cart
Wix Cart/Ecom shared package for Jay Framework
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@wix/sdk-runtime | AI (phantom-deps): Declared as runtime dep, likely used transitively or via config; stable false positive for this framework package. | ai | |
| phantom-deps | phantom-dep:@jay-framework/secure | AI (phantom-deps): Same-org dependency; likely used indirectly via re-exports in this framework package. | ai | |
| phantom-deps | phantom-dep:@jay-framework/wix-utils | AI (phantom-deps): Same-org dependency; likely used indirectly via re-exports in this framework package. | ai | |
| phantom-deps | phantom-dep:@jay-framework/stack-client-runtime | AI (phantom-deps): Same-org dependency; likely used indirectly via re-exports in this framework package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.18.0 | 12 / 14 | |
| 0.17.4 | 12 / 14 | |
| 0.17.3 | 12 / 14 | |
| 0.17.2 | 12 / 14 | |
| 0.17.1 | 12 / 14 | |
| 0.17.0 | 12 / 14 | |
| 0.16.5 | 12 / 14 | |
| 0.16.4 | 12 / 14 | |
| 0.16.3 | 12 / 14 | |
| 0.16.2 | 12 / 14 | |
| 0.16.1 | 12 / 14 | |
| 0.16.0 | 12 / 14 | |
| 0.15.6 | 12 / 14 | |
| 0.15.5 | 12 / 14 | |
| 0.15.4 | 11 / 14 | |
| 0.15.1 | 11 / 14 | |
| 0.15.0 | 11 / 14 |
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.