@wix/app-management
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Wix internal monorepo package; mass-produced naming and missing metadata are expected for this publisher's packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Wix internal SDK package; missing description is a consistent pattern across their packages, not a malware signal. | ai | |
| provenance | no-provenance | AI (provenance): Wix CI publisher has 1089 approved packages without provenance; stable pattern for this publisher. | ai |
Versions (showing 100 of 137)
| Version | Deps | Published |
|---|---|---|
| 1.0.155 | 8 / 2 | |
| 1.0.154 | 8 / 2 | |
| 1.0.153 | 8 / 2 | |
| 1.0.152 | 8 / 2 | |
| 1.0.151 | 8 / 2 | |
| 1.0.150 | 8 / 2 | |
| 1.0.149 | 8 / 2 | |
| 1.0.148 | 8 / 2 | |
| 1.0.147 | 8 / 2 | |
| 1.0.146 | 8 / 2 | |
| 1.0.145 | 8 / 2 | |
| 1.0.144 | 8 / 2 | |
| 1.0.143 | 8 / 2 | |
| 1.0.142 | 8 / 2 | |
| 1.0.141 | 8 / 2 | |
| 1.0.140 | 8 / 2 | |
| 1.0.139 | 8 / 2 | |
| 1.0.138 | 8 / 2 | |
| 1.0.137 | 8 / 2 | |
| 1.0.136 | 8 / 2 | |
| 1.0.135 | 8 / 2 | |
| 1.0.134 | 8 / 2 | |
| 1.0.133 | 8 / 2 | |
| 1.0.132 | 8 / 2 | |
| 1.0.131 | 8 / 2 | |
| 1.0.130 | 8 / 2 | |
| 1.0.129 | 8 / 2 | |
| 1.0.126 | 8 / 2 | |
| 1.0.125 | 8 / 2 | |
| 1.0.124 | 8 / 2 | |
| 1.0.123 | 8 / 2 | |
| 1.0.122 | 8 / 2 | |
| 1.0.121 | 8 / 2 | |
| 1.0.120 | 8 / 2 | |
| 1.0.119 | 8 / 2 | |
| 1.0.118 | 8 / 2 | |
| 1.0.117 | 8 / 2 | |
| 1.0.116 | 8 / 2 | |
| 1.0.115 | 8 / 2 | |
| 1.0.114 | 8 / 2 | |
| 1.0.113 | 8 / 2 | |
| 1.0.112 | 8 / 2 | |
| 1.0.111 | 8 / 2 | |
| 1.0.110 | 8 / 2 | |
| 1.0.109 | 8 / 2 | |
| 1.0.108 | 8 / 2 | |
| 1.0.107 | 8 / 2 | |
| 1.0.106 | 8 / 2 | |
| 1.0.105 | 8 / 2 | |
| 1.0.104 | 8 / 2 | |
| 1.0.103 | 8 / 2 | |
| 1.0.102 | 8 / 2 | |
| 1.0.101 | 8 / 1 | |
| 1.0.100 | 8 / 1 | |
| 1.0.99 | 8 / 1 | |
| 1.0.98 | 8 / 1 | |
| 1.0.97 | 8 / 1 | |
| 1.0.96 | 8 / 1 | |
| 1.0.95 | 8 / 1 | |
| 1.0.94 | 8 / 1 | |
| 1.0.93 | 8 / 1 | |
| 1.0.92 | 8 / 1 | |
| 1.0.91 | 8 / 1 | |
| 1.0.90 | 8 / 1 | |
| 1.0.89 | 8 / 1 | |
| 1.0.88 | 8 / 1 | |
| 1.0.87 | 8 / 1 | |
| 1.0.86 | 8 / 1 | |
| 1.0.85 | 7 / 1 | |
| 1.0.84 | 7 / 2 | |
| 1.0.83 | 7 / 2 | |
| 1.0.82 | 7 / 2 | |
| 1.0.81 | 7 / 1 | |
| 1.0.80 | 7 / 1 | |
| 1.0.79 | 7 / 1 | |
| 1.0.78 | 7 / 1 | |
| 1.0.77 | 7 / 1 | |
| 1.0.76 | 7 / 1 | |
| 1.0.75 | 7 / 1 | |
| 1.0.74 | 7 / 1 | |
| 1.0.73 | 6 / 1 | |
| 1.0.72 | 6 / 1 | |
| 1.0.71 | 6 / 1 | |
| 1.0.70 | 6 / 1 | |
| 1.0.69 | 6 / 1 | |
| 1.0.68 | 6 / 1 | |
| 1.0.67 | 6 / 1 | |
| 1.0.66 | 6 / 1 | |
| 1.0.65 | 6 / 1 | |
| 1.0.64 | 6 / 1 | |
| 1.0.63 | 6 / 1 | |
| 1.0.62 | 6 / 1 | |
| 1.0.61 | 6 / 1 | |
| 1.0.60 | 6 / 1 | |
| 1.0.59 | 6 / 1 | |
| 1.0.58 | 6 / 1 | |
| 1.0.57 | 6 / 1 | |
| 1.0.56 | 6 / 1 | |
| 1.0.55 | 6 / 1 | |
| 1.0.54 | 6 / 1 |
v1.0.155
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.