@rescui/adaptive-switcher
* [Usage examples](./docs/demo.md)
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): Internal JetBrains UI component; sparse metadata is a stable pattern across this package family. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with JetBrains internal component publishing style; not a malware indicator here. | ai | |
| phantom-deps | phantom-dep:@babel/runtime-corejs3 | AI (phantom-deps): Babel runtime is injected by the build toolchain, not directly imported in source. | ai |
Versions (showing 58 of 58)
| Version | Deps | Published |
|---|---|---|
| 0.8.9 | 5 / 1 | |
| 0.8.8 | 5 / 1 | |
| 0.8.7 | 5 / 1 | |
| 0.8.6 | 5 / 1 | |
| 0.8.5 | 5 / 1 | |
| 0.8.4 | 5 / 1 | |
| 0.8.3 | 5 / 1 | |
| 0.8.2 | 5 / 1 | |
| 0.8.1 | 5 / 1 | |
| 0.8.0 | 5 / 1 | |
| 0.7.7 | 5 / 1 | |
| 0.7.6 | 5 / 1 | |
| 0.7.5 | 5 / 1 | |
| 0.7.4 | 5 / 1 | |
| 0.7.3 | 5 / 1 | |
| 0.7.2 | 5 / 1 | |
| 0.7.1 | 5 / 1 | |
| 0.7.0 | 5 / 1 | |
| 0.6.6 | 5 / 1 | |
| 0.6.5 | 5 / 1 | |
| 0.6.4 | 5 / 1 | |
| 0.6.3 | 5 / 1 | |
| 0.6.2 | 5 / 1 | |
| 0.6.1 | 5 / 1 | |
| 0.6.0 | 5 / 1 | |
| 0.5.5 | 5 / 1 | |
| 0.5.4 | 5 / 1 | |
| 0.5.3 | 5 / 1 | |
| 0.5.2 | 5 / 1 | |
| 0.5.1 | 6 / 1 | |
| 0.5.0 | 6 / 1 | |
| 0.4.13 | 6 / 1 | |
| 0.4.12 | 6 / 1 | |
| 0.4.11 | 6 / 1 | |
| 0.4.10 | 6 / 1 | |
| 0.4.9 | 6 / 1 | |
| 0.4.8 | 6 / 1 | |
| 0.4.7 | 6 / 1 | |
| 0.4.6 | 6 / 1 | |
| 0.4.5 | 6 / 1 | |
| 0.4.4 | 6 / 1 | |
| 0.4.3 | 6 / 1 | |
| 0.4.2 | 6 / 1 | |
| 0.4.1 | 6 / 1 | |
| 0.4.0 | 6 / 1 | |
| 0.3.3 | 6 / 1 | |
| 0.3.2 | 6 / 1 | |
| 0.3.1 | 6 / 1 | |
| 0.3.0 | 6 / 1 | |
| 0.2.1 | 6 / 1 | |
| 0.2.0 | 6 / 1 | |
| 0.1.24 | 6 / 1 | |
| 0.1.23 | 6 / 1 | |
| 0.1.22 | 6 / 1 | |
| 0.1.21 | 6 / 1 | |
| 0.1.20 | 6 / 1 | |
| 0.1.19 | 6 / 1 | |
| 0.1.18 | 6 / 1 |
v0.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.