@rxdi/http
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Established package family; missing description is a consistent pattern across rxdi packages, not a malice indicator. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across all 182 versions; stable pattern for this publisher. | ai |
Versions (showing 100 of 187)
| Version | Deps | Published |
|---|---|---|
| 0.7.250 | 2 / 4 | |
| 0.7.249 | 2 / 4 | |
| 0.7.248 | 2 / 4 | |
| 0.7.247 | 2 / 4 | |
| 0.7.246 | 2 / 4 | |
| 0.7.245 | 2 / 4 | |
| 0.7.244 | 2 / 4 | |
| 0.7.243 | 2 / 4 | |
| 0.7.242 | 2 / 4 | |
| 0.7.241 | 2 / 4 | |
| 0.7.240 | 2 / 4 | |
| 0.7.239 | 2 / 8 | |
| 0.7.238 | 2 / 8 | |
| 0.7.237 | 2 / 8 | |
| 0.7.236 | 2 / 8 | |
| 0.7.235 | 2 / 8 | |
| 0.7.234 | 2 / 8 | |
| 0.7.233 | 2 / 8 | |
| 0.7.232 | 2 / 8 | |
| 0.7.231 | 2 / 8 | |
| 0.7.230 | 2 / 8 | |
| 0.7.229 | 2 / 8 | |
| 0.7.228 | 2 / 8 | |
| 0.7.227 | 2 / 8 | |
| 0.7.226 | 2 / 8 | |
| 0.7.225 | 2 / 8 | |
| 0.7.224 | 2 / 8 | |
| 0.7.223 | 2 / 8 | |
| 0.7.222 | 2 / 8 | |
| 0.7.221 | 2 / 8 | |
| 0.7.220 | 2 / 8 | |
| 0.7.219 | 2 / 8 | |
| 0.7.218 | 2 / 8 | |
| 0.7.217 | 2 / 8 | |
| 0.7.216 | 2 / 8 | |
| 0.7.215 | 2 / 8 | |
| 0.7.214 | 2 / 8 | |
| 0.7.213 | 2 / 8 | |
| 0.7.212 | 2 / 8 | |
| 0.7.211 | 2 / 8 | |
| 0.7.210 | 2 / 8 | |
| 0.7.209 | 2 / 8 | |
| 0.7.208 | 2 / 8 | |
| 0.7.207 | 2 / 8 | |
| 0.7.206 | 2 / 8 | |
| 0.7.205 | 2 / 8 | |
| 0.7.204 | 2 / 8 | |
| 0.7.203 | 2 / 8 | |
| 0.7.202 | 2 / 8 | |
| 0.7.201 | 2 / 8 | |
| 0.7.200 | 2 / 8 | |
| 0.7.199 | 2 / 8 | |
| 0.7.198 | 2 / 8 | |
| 0.7.197 | 2 / 8 | |
| 0.7.196 | 2 / 8 | |
| 0.7.195 | 2 / 8 | |
| 0.7.194 | 2 / 8 | |
| 0.7.193 | 2 / 8 | |
| 0.7.192 | 2 / 8 | |
| 0.7.191 | 2 / 8 | |
| 0.7.190 | 2 / 8 | |
| 0.7.189 | 2 / 8 | |
| 0.7.188 | 2 / 8 | |
| 0.7.187 | 2 / 8 | |
| 0.7.186 | 2 / 8 | |
| 0.7.185 | 2 / 8 | |
| 0.7.184 | 2 / 8 | |
| 0.7.183 | 2 / 8 | |
| 0.7.182 | 2 / 8 | |
| 0.7.181 | 2 / 8 | |
| 0.7.180 | 2 / 8 | |
| 0.7.179 | 2 / 8 | |
| 0.7.178 | 2 / 8 | |
| 0.7.177 | 2 / 8 | |
| 0.7.176 | 2 / 8 | |
| 0.7.175 | 2 / 8 | |
| 0.7.174 | 2 / 8 | |
| 0.7.173 | 2 / 8 | |
| 0.7.172 | 2 / 8 | |
| 0.7.171 | 2 / 8 | |
| 0.7.170 | 2 / 8 | |
| 0.7.169 | 2 / 8 | |
| 0.7.168 | 2 / 8 | |
| 0.7.167 | 2 / 8 | |
| 0.7.166 | 2 / 8 | |
| 0.7.165 | 2 / 8 | |
| 0.7.164 | 2 / 8 | |
| 0.7.163 | 2 / 8 | |
| 0.7.162 | 2 / 8 | |
| 0.7.161 | 2 / 8 | |
| 0.7.160 | 2 / 8 | |
| 0.7.159 | 2 / 8 | |
| 0.7.158 | 2 / 8 | |
| 0.7.157 | 2 / 8 | |
| 0.7.156 | 2 / 8 | |
| 0.7.155 | 2 / 8 | |
| 0.7.154 | 2 / 8 | |
| 0.7.153 | 2 / 8 | |
| 0.7.152 | 2 / 8 | |
| 0.7.151 | 2 / 8 |
v0.7.250
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.180
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.179
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.178
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.177
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.176
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.175
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.174
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.173
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.172
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.171
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.170
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.169
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.168
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.167
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.166
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.165
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.164
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.163
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.162
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.161
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.160
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.159
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.158
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.157
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.156
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.155
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.154
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.153
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.152
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.151
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.