@rescui/input
* [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): JetBrains internal UI component library; sparse metadata is consistent across all 134 versions of this scoped package. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 0.15.7 | 3 / 8 | |
| 0.15.6 | 3 / 8 | |
| 0.15.5 | 3 / 8 | |
| 0.15.4 | 3 / 8 | |
| 0.15.3 | 3 / 8 | |
| 0.15.2 | 3 / 8 | |
| 0.15.1 | 3 / 8 | |
| 0.14.5 | 2 / 8 | |
| 0.14.4 | 2 / 8 | |
| 0.14.3 | 2 / 8 | |
| 0.14.2 | 2 / 8 | |
| 0.14.1 | 2 / 8 | |
| 0.14.0 | 2 / 8 | |
| 0.13.0 | 2 / 8 | |
| 0.12.4 | 2 / 8 | |
| 0.12.3 | 2 / 8 | |
| 0.12.2 | 2 / 8 | |
| 0.12.1 | 2 / 8 | |
| 0.12.0 | 2 / 8 | |
| 0.11.20 | 2 / 8 | |
| 0.11.19 | 2 / 8 | |
| 0.11.18 | 2 / 8 | |
| 0.11.17 | 2 / 8 | |
| 0.11.16 | 2 / 8 | |
| 0.11.15 | 2 / 8 | |
| 0.11.14 | 2 / 8 | |
| 0.11.13 | 2 / 8 | |
| 0.11.12 | 2 / 8 | |
| 0.11.11 | 2 / 8 | |
| 0.11.10 | 2 / 8 | |
| 0.11.9 | 2 / 8 | |
| 0.11.8 | 3 / 8 | |
| 0.11.7 | 3 / 8 | |
| 0.11.6 | 3 / 8 | |
| 0.11.5 | 3 / 8 | |
| 0.11.4 | 3 / 8 | |
| 0.11.3 | 3 / 8 | |
| 0.11.2 | 3 / 8 | |
| 0.11.1 | 3 / 8 | |
| 0.11.0 | 3 / 8 | |
| 0.10.4 | 4 / 7 | |
| 0.10.3 | 4 / 7 | |
| 0.10.2 | 4 / 7 | |
| 0.10.1 | 4 / 7 | |
| 0.10.0 | 4 / 7 | |
| 0.9.9 | 4 / 7 | |
| 0.9.8 | 4 / 7 | |
| 0.9.7 | 4 / 7 | |
| 0.9.6 | 4 / 7 |
v0.15.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.