jshint-stylish
Stylish reporter for JSHint
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
Keywords
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 2.2.1 | 6 / 3 | |
| 2.2.0 | 6 / 3 | |
| 2.1.0 | 5 / 2 | |
| 2.0.1 | 5 / 2 | |
| 2.0.0 | 4 / 2 | |
| 1.0.2 | 4 / 2 | |
| 1.0.1 | 4 / 2 | |
| 1.0.0 | 4 / 2 | |
| 0.4.0 | 3 / 2 | |
| 0.3.0 | 2 / 2 | |
| 0.2.0 | 2 / 2 | |
| 0.1.5 | 2 / 2 | |
| 0.1.4 | 2 / 2 | |
| 0.1.3 | 2 / 2 | |
| 0.1.2 | 2 / 2 | |
| 0.1.1 | 2 / 2 | |
| 0.1.0 | 2 / 2 |
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.