@artel/standard-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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@artel/ru-platform-javascript | AI (phantom-deps): Same-org phantom dep, consistent with all other @artel/* phantom deps already accepted. | ai | |
| dependencies | unvetted-dep:@artel/en-user-interface | AI (dependencies): Same-org @artel/* dependency; consistent with this package's role as a bundle of artel components. | ai | |
| dependencies | unvetted-dep:@artel/ru-user-interface | AI (dependencies): Same-org @artel/* dependency; consistent with this package's role as a bundle of artel components. | ai | |
| bogus-package | bogus-package | AI (bogus-package): No-repo/tiny-payload pattern is consistent across all @artel distribution packages; not indicative of spam. | ai | |
| phantom-deps | phantom-dep:@artel/en-user-interface | AI (phantom-deps): Same-org @artel package; consistent phantom-dep pattern for this package. | ai | |
| phantom-deps | phantom-dep:@artel/ru-user-interface | AI (phantom-deps): Same-org @artel package; consistent phantom-dep pattern for this package. | ai | |
| phantom-deps | phantom-dep:@artel/ru-artel-system | AI (phantom-deps): Same-org @artel package; consistent phantom-dep pattern for this package. | ai | |
| phantom-deps | phantom-dep:@artel/en-artel-system | AI (phantom-deps): Same-org @artel package; consistent phantom-dep pattern for this package. | ai | |
| phantom-deps | phantom-dep:@artel/ru-compiler | AI (phantom-deps): Same-org @artel package; phantom-dep pattern is stable across this package's many versions. | ai | |
| phantom-deps | phantom-dep:@artel/ru-verstak | AI (phantom-deps): Same umbrella pattern. | ai | |
| phantom-deps | phantom-dep:@artel/en-reactivity | AI (phantom-deps): Same umbrella pattern. | ai | |
| phantom-deps | phantom-dep:@artel/ru-reactivity | AI (phantom-deps): Same umbrella pattern. | ai | |
| phantom-deps | phantom-dep:@artel/en-platform-javascript | AI (phantom-deps): Same umbrella pattern. | ai | |
| phantom-deps | phantom-dep:@artel/en-platform-javascript-intl | AI (phantom-deps): Same umbrella pattern. | ai | |
| phantom-deps | phantom-dep:@artel/en-math | AI (phantom-deps): Umbrella package; deps declared for re-export, not direct import. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@artel/ru-platform-javascript-intl | AI (phantom-deps): Same umbrella pattern. | ai | |
| phantom-deps | phantom-dep:@artel/ru-platform-javascript-node | AI (phantom-deps): Same umbrella pattern. | ai | |
| phantom-deps | phantom-dep:@artel/en-platform-javascript-console | AI (phantom-deps): Same umbrella pattern. | ai | |
| phantom-deps | phantom-dep:@artel/artc | AI (phantom-deps): Same umbrella pattern. | ai | |
| phantom-deps | phantom-dep:@artel/en-compiler | AI (phantom-deps): Same umbrella pattern. | ai | |
| phantom-deps | phantom-dep:@artel/en-platform-javascript-node | AI (phantom-deps): Same umbrella pattern. | ai | |
| phantom-deps | phantom-dep:@artel/ru-math | AI (phantom-deps): Same umbrella pattern. | ai | |
| phantom-deps | phantom-dep:@artel/en-dialog | AI (phantom-deps): Same umbrella pattern. | ai | |
| phantom-deps | phantom-dep:@artel/ru-dialog | AI (phantom-deps): Same umbrella pattern. | ai | |
| phantom-deps | phantom-dep:@artel/en-browser | AI (phantom-deps): Same umbrella pattern. | ai | |
| phantom-deps | phantom-dep:@artel/en-logging | AI (phantom-deps): Same umbrella pattern. | ai | |
| phantom-deps | phantom-dep:@artel/en-verstak | AI (phantom-deps): Same umbrella pattern. | ai | |
| phantom-deps | phantom-dep:@artel/ru-browser | AI (phantom-deps): Same umbrella pattern. | ai | |
| phantom-deps | phantom-dep:@artel/ru-logging | AI (phantom-deps): Same umbrella pattern. | ai |
Versions (showing 51 of 54)
| Version | Deps | Published |
|---|---|---|
| 0.9.26021 | 24 / 0 | |
| 0.9.26016 | 23 / 0 | |
| 0.9.26008 | 23 / 0 | |
| 0.9.26003 | 23 / 0 | |
| 0.9.26002 | 23 / 0 | |
| 0.9.26001 | 23 / 0 | |
| 0.8.26001 | 23 / 0 | |
| 0.6.26039 | 23 / 0 | |
| 0.6.26038 | 23 / 0 | |
| 0.6.26037 | 23 / 0 | |
| 0.6.26036 | 23 / 0 | |
| 0.6.26035 | 23 / 0 | |
| 0.6.26034 | 23 / 0 | |
| 0.6.26033 | 23 / 0 | |
| 0.6.26032 | 23 / 0 | |
| 0.6.26031 | 23 / 0 | |
| 0.6.26030 | 23 / 0 | |
| 0.6.26029 | 23 / 0 | |
| 0.6.26028 | 23 / 0 | |
| 0.6.26027 | 23 / 0 | |
| 0.6.26026 | 23 / 0 | |
| 0.6.26025 | 23 / 0 | |
| 0.6.26024 | 23 / 0 | |
| 0.6.26023 | 23 / 0 | |
| 0.6.26022 | 23 / 0 | |
| 0.6.26021 | 23 / 0 | |
| 0.6.26020 | 23 / 0 | |
| 0.6.26019 | 23 / 0 | |
| 0.6.26018 | 23 / 0 | |
| 0.6.26017 | 23 / 0 | |
| 0.6.26016 | 23 / 0 | |
| 0.6.26015 | 23 / 0 | |
| 0.6.26014 | 23 / 0 | |
| 0.6.26013 | 23 / 0 | |
| 0.6.26012 | 23 / 0 | |
| 0.6.26011 | 23 / 0 | |
| 0.6.26010 | 23 / 0 | |
| 0.6.26009 | 23 / 0 | |
| 0.6.26008 | 23 / 0 | |
| 0.6.26007 | 23 / 0 | |
| 0.6.26003 | 23 / 0 | |
| 0.6.25297 | 23 / 0 | |
| 0.6.25296 | 23 / 0 | |
| 0.6.25294 | 23 / 0 | |
| 0.6.25292 | 23 / 0 | |
| 0.6.25290 | 23 / 0 | |
| 0.6.25289 | 23 / 0 | |
| 0.6.25286 | 23 / 0 | |
| 0.6.25283 | 23 / 0 | |
| 0.6.25281 | 23 / 0 | |
| 0.6.25279 | 23 / 0 |
v0.9.26021
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26038
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26037
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.26022
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.26021
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.26020
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.26019
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.26018
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.26017
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.26016
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.26015
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.26014
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.26013
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.26012
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.26011
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.26010
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.26009
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.26008
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.26007
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.26003
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25297
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25296
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25294
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25292
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25290
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25289
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25286
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25283
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25281
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25279
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.