@artel/ru-compiler
*А* Артель.Компилятор (RU)
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
Versions (showing 51 of 86)
| Version | Deps | Published |
|---|---|---|
| 0.9.26021 | 0 / 0 | |
| 0.9.26020 | 0 / 0 | |
| 0.9.26016 | 0 / 0 | |
| 0.9.26008 | 0 / 0 | |
| 0.9.26003 | 0 / 0 | |
| 0.9.26002 | 0 / 0 | |
| 0.9.26001 | 0 / 0 | |
| 0.8.26001 | 0 / 0 | |
| 0.6.26039 | 0 / 0 | |
| 0.6.26038 | 0 / 0 | |
| 0.6.26036 | 0 / 0 | |
| 0.6.26035 | 0 / 0 | |
| 0.6.26034 | 0 / 0 | |
| 0.6.26033 | 0 / 0 | |
| 0.6.26032 | 0 / 0 | |
| 0.6.26031 | 0 / 0 | |
| 0.6.26030 | 0 / 0 | |
| 0.6.26029 | 0 / 0 | |
| 0.6.26028 | 0 / 0 | |
| 0.6.26027 | 0 / 0 | |
| 0.6.26026 | 0 / 0 | |
| 0.6.26025 | 0 / 0 | |
| 0.6.26024 | 0 / 0 | |
| 0.6.26023 | 0 / 0 | |
| 0.6.26022 | 0 / 0 | |
| 0.6.26021 | 0 / 0 | |
| 0.6.26020 | 0 / 0 | |
| 0.6.26019 | 0 / 0 | |
| 0.6.26018 | 0 / 0 | |
| 0.6.26017 | 0 / 0 | |
| 0.6.26016 | 0 / 0 | |
| 0.6.26015 | 0 / 0 | |
| 0.6.26014 | 0 / 0 | |
| 0.6.26013 | 0 / 0 | |
| 0.6.26012 | 0 / 0 | |
| 0.6.26011 | 0 / 0 | |
| 0.6.26010 | 0 / 0 | |
| 0.6.26009 | 0 / 0 | |
| 0.6.26008 | 0 / 0 | |
| 0.6.26007 | 0 / 0 | |
| 0.6.26006 | 0 / 0 | |
| 0.6.26005 | 0 / 0 | |
| 0.6.26004 | 0 / 0 | |
| 0.6.26003 | 0 / 0 | |
| 0.6.26002 | 0 / 0 | |
| 0.6.26001 | 0 / 0 | |
| 0.6.25297 | 0 / 0 | |
| 0.6.25296 | 0 / 0 | |
| 0.6.25295 | 0 / 0 | |
| 0.6.25294 | 0 / 0 | |
| 0.6.25293 | 0 / 0 |
v0.9.26021
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.26020
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.26016
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.26008
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.26003
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.26002
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.26001
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.26001
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26039
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.26038
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26036
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26035
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26034
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26033
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26032
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26031
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26030
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26029
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26028
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26027
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26026
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26025
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26024
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.26023
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26022
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26021
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26020
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26019
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26018
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26017
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26016
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26015
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26014
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26013
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26012
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26011
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26010
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26009
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26008
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26007
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26006
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26005
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26004
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26003
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26002
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26001
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.25297
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.25296
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.25295
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.25294
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.25293
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.