@alexlit/lint-kit
Preset of configuration files and dependencies for linting web applications (designed for Vue.js with TypeScript)
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established publisher with strong approval track record; no material changes in this version. | ai | |
| source-diff | obfuscated-file:packages/config-stylelint/node_modules/meow/build/dependencies.js | AI (source-diff): Minified build artifact from the legitimate meow package; not obfuscated malware. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Size increase due to bundled node_modules in monorepo package; not injected payload. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Tripling explained by inclusion of node_modules (rxjs etc.) in tarball; benign packaging artifact. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Long-lived monorepo; preinstall.sh is a standard workspace setup script with no malicious indicators. | ai | |
| provenance | no-provenance | AI (provenance): Established package with consistent publishing history; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 186.3.1 | 0 / 1 | |
| 186.1.0 | 0 / 1 | |
| 186.0.0 | 0 / 1 | |
| 185.12.0 | 0 / 1 | |
| 185.10.1 | 0 / 1 | |
| 185.9.0 | 0 / 1 | |
| 185.7.0 | 0 / 1 | |
| 185.5.1 | 0 / 1 | |
| 185.5.0 | 0 / 1 | |
| 185.3.2 | 0 / 1 | |
| 185.3.1 | 0 / 1 | |
| 185.3.0 | 0 / 1 | |
| 185.1.0 | 0 / 1 | |
| 185.0.0 | 0 / 1 | |
| 183.6.0 | 0 / 1 | |
| 164.9.1 | 0 / 1 | |
| 164.9.0 | 0 / 1 | |
| 164.5.0 | 0 / 1 | |
| 164.3.1 | 0 / 1 | |
| 164.2.0 | 0 / 1 | |
| 164.0.0 | 0 / 1 | |
| 163.2.3 | 0 / 1 |
v186.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v186.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v186.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v185.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v185.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v185.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v185.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v185.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v185.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v185.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v185.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v185.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v185.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v183.6.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v164.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v164.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v164.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v164.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v164.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v164.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v163.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.