@jay-framework/wix-data
Wix Data plugin for Jay Framework with dynamic contract generation
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): Newly added runtime dep used via framework internals, not direct import; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@jay-framework/secure | AI (phantom-deps): Same-org monorepo dep; likely re-exported or used indirectly via peer packages. | ai | |
| phantom-deps | phantom-dep:@jay-framework/reactive | AI (phantom-deps): Same-org monorepo dep; likely re-exported or used indirectly via peer packages. | ai | |
| phantom-deps | phantom-dep:@jay-framework/wix-utils | AI (phantom-deps): Same-org monorepo dep; likely re-exported or used indirectly via peer packages. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.18.0 | 13 / 15 | |
| 0.17.4 | 13 / 15 | |
| 0.17.3 | 13 / 15 | |
| 0.17.2 | 13 / 15 | |
| 0.17.1 | 13 / 15 | |
| 0.17.0 | 13 / 15 | |
| 0.16.5 | 13 / 15 | |
| 0.16.4 | 13 / 15 | |
| 0.16.3 | 13 / 15 | |
| 0.16.2 | 13 / 15 | |
| 0.16.1 | 13 / 15 | |
| 0.16.0 | 13 / 15 | |
| 0.15.6 | 13 / 15 | |
| 0.15.5 | 13 / 15 | |
| 0.15.4 | 12 / 15 | |
| 0.15.1 | 12 / 15 | |
| 0.15.0 | 12 / 15 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.