@live-change/email-service
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
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): Legitimate monorepo service package; sparse README/metadata is consistent across the live-change-stack ecosystem. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across live-change-stack packages; not a spam indicator here. | ai | |
| phantom-deps | phantom-dep:inline-css | AI (phantom-deps): inline-css is listed as a runtime dependency in package.json; phantom-dep is a false positive here. | ai |
Versions (showing 100 of 339)
| Version | Deps | Published |
|---|---|---|
| 0.9.216 | 10 / 0 | |
| 0.9.215 | 10 / 0 | |
| 0.9.214 | 10 / 0 | |
| 0.9.213 | 10 / 0 | |
| 0.9.212 | 10 / 0 | |
| 0.9.209 | 10 / 0 | |
| 0.9.208 | 10 / 0 | |
| 0.9.207 | 10 / 0 | |
| 0.9.206 | 10 / 0 | |
| 0.9.205 | 10 / 0 | |
| 0.9.204 | 10 / 0 | |
| 0.9.203 | 10 / 0 | |
| 0.9.201 | 10 / 0 | |
| 0.9.200 | 10 / 0 | |
| 0.9.199 | 10 / 0 | |
| 0.9.198 | 10 / 0 | |
| 0.9.197 | 10 / 0 | |
| 0.9.196 | 10 / 0 | |
| 0.9.195 | 10 / 0 | |
| 0.9.194 | 10 / 0 | |
| 0.9.193 | 10 / 0 | |
| 0.9.192 | 10 / 0 | |
| 0.9.191 | 10 / 0 | |
| 0.9.190 | 10 / 0 | |
| 0.9.189 | 10 / 0 | |
| 0.9.188 | 10 / 0 | |
| 0.9.187 | 10 / 0 | |
| 0.9.186 | 10 / 0 | |
| 0.9.185 | 10 / 0 | |
| 0.9.184 | 10 / 0 | |
| 0.9.183 | 10 / 0 | |
| 0.9.182 | 10 / 0 | |
| 0.9.181 | 10 / 0 | |
| 0.9.180 | 10 / 0 | |
| 0.9.179 | 10 / 0 | |
| 0.9.177 | 10 / 0 | |
| 0.9.176 | 10 / 0 | |
| 0.9.175 | 10 / 0 | |
| 0.9.174 | 10 / 0 | |
| 0.9.173 | 10 / 0 | |
| 0.9.171 | 10 / 0 | |
| 0.9.169 | 10 / 0 | |
| 0.9.167 | 10 / 0 | |
| 0.9.166 | 10 / 0 | |
| 0.9.165 | 10 / 0 | |
| 0.9.164 | 10 / 0 | |
| 0.9.163 | 10 / 0 | |
| 0.9.162 | 10 / 0 | |
| 0.9.161 | 10 / 0 | |
| 0.9.160 | 10 / 0 | |
| 0.9.159 | 10 / 0 | |
| 0.9.158 | 10 / 0 | |
| 0.9.157 | 10 / 0 | |
| 0.9.156 | 10 / 0 | |
| 0.9.155 | 10 / 0 | |
| 0.9.154 | 10 / 0 | |
| 0.9.153 | 10 / 0 | |
| 0.9.152 | 10 / 0 | |
| 0.9.151 | 10 / 0 | |
| 0.9.150 | 10 / 0 | |
| 0.9.149 | 10 / 0 | |
| 0.9.148 | 10 / 0 | |
| 0.9.147 | 10 / 0 | |
| 0.9.146 | 10 / 0 | |
| 0.9.145 | 10 / 0 | |
| 0.9.144 | 10 / 0 | |
| 0.9.143 | 10 / 0 | |
| 0.9.142 | 10 / 0 | |
| 0.9.141 | 10 / 0 | |
| 0.9.140 | 10 / 0 | |
| 0.9.139 | 10 / 0 | |
| 0.9.138 | 10 / 0 | |
| 0.9.137 | 10 / 0 | |
| 0.9.136 | 10 / 0 | |
| 0.9.135 | 10 / 0 | |
| 0.9.134 | 10 / 0 | |
| 0.9.133 | 10 / 0 | |
| 0.9.132 | 10 / 0 | |
| 0.9.131 | 10 / 0 | |
| 0.9.130 | 10 / 0 | |
| 0.9.129 | 10 / 0 | |
| 0.9.128 | 10 / 0 | |
| 0.9.127 | 10 / 0 | |
| 0.9.126 | 10 / 0 | |
| 0.9.125 | 10 / 0 | |
| 0.9.124 | 10 / 0 | |
| 0.9.123 | 10 / 0 | |
| 0.9.122 | 10 / 0 | |
| 0.9.121 | 10 / 0 | |
| 0.9.120 | 10 / 0 | |
| 0.9.119 | 10 / 0 | |
| 0.9.118 | 10 / 0 | |
| 0.9.117 | 10 / 0 | |
| 0.9.116 | 10 / 0 | |
| 0.9.115 | 10 / 0 | |
| 0.9.114 | 10 / 0 | |
| 0.9.113 | 10 / 0 | |
| 0.9.112 | 10 / 0 | |
| 0.9.111 | 10 / 0 | |
| 0.9.110 | 10 / 0 |
v0.9.216
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.215
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.214
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.213
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.212
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.201
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.200
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.199
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.197
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.196
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.193
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.191
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.189
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.187
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.185
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.184
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.182
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.179
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.175
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.173
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.169
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.167
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.164
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.160
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.159
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.158
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.155
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.154
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.151
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.150
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.148
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.147
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.145
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.144
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.143
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.141
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.140
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.138
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.136
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.134
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.133
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.131
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.130
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.129
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.127
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.126
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.124
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.123
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.121
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.119
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.117
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.115
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.113
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.112
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.