@artel/compact-edition
*А* Артель Компактная Редакция | Artel Compact Edition
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Intentional thin meta/alias package pattern within @artel org; tiny payload and no repo are expected for this type. | ai | |
| phantom-deps | phantom-dep:@artel/artc | AI (phantom-deps): Same-org scoped dep; tiny package with no code files makes import detection unreliable. | ai |
Versions (showing 21 of 121)
| Version | Deps | Published |
|---|---|---|
| 0.6.25243 | 1 / 0 | |
| 0.6.25242 | 1 / 0 | |
| 0.6.25241 | 1 / 0 | |
| 0.6.25240 | 1 / 0 | |
| 0.6.25239 | 1 / 0 | |
| 0.6.25238 | 1 / 0 | |
| 0.6.25237 | 1 / 0 | |
| 0.6.25236 | 1 / 0 | |
| 0.6.25235 | 1 / 0 | |
| 0.6.25234 | 1 / 0 | |
| 0.6.25233 | 1 / 0 | |
| 0.6.25232 | 1 / 0 | |
| 0.6.25231 | 1 / 0 | |
| 0.6.25230 | 1 / 0 | |
| 0.6.25229 | 1 / 0 | |
| 0.6.25228 | 1 / 0 | |
| 0.6.25227 | 1 / 0 | |
| 0.6.25226 | 1 / 0 | |
| 0.6.25225 | 1 / 0 | |
| 0.6.25224 | 1 / 0 | |
| 0.6.25223 | 1 / 0 |
v0.6.25243
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25242
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25241
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25240
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25239
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25238
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25237
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25236
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25235
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25234
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25233
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25232
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25231
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25230
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25229
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25228
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25227
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25226
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25225
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25224
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25223
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.