@cabloy/lint
Node Style Guide for Cabloy.
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:eslint-plugin-unused-imports | AI (phantom-deps): ESLint plugin loaded by config convention, not direct import; stable pattern for this lint preset package. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-toml | AI (phantom-deps): ESLint plugin loaded by config convention, not direct import; stable pattern for this lint preset package. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-regexp | AI (phantom-deps): ESLint plugin loaded by config convention, not direct import; stable pattern for this lint preset package. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-command | AI (phantom-deps): ESLint plugin loaded by config convention, not direct import; stable pattern for this lint preset package. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-pnpm | AI (phantom-deps): ESLint plugin loaded by config convention, not direct import; stable pattern for this lint preset package. | ai | |
| dependencies | unvetted-dep:@antfu/eslint-config | AI (dependencies): @antfu/eslint-config is a widely-used, well-known ESLint config; stable false positive for this lint config package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of the Cabloy framework monorepo; mass-production pattern is expected for this publisher's scoped packages. | ai | |
| phantom-deps | phantom-dep:vue-eslint-parser | AI (phantom-deps): ESLint config packages load plugins by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/parser | AI (phantom-deps): ESLint config package; plugins are loaded by convention in config files, not direct imports. | ai | |
| typosquat | typosquat.levenshtein:eslint | AI (typosquat): Scoped package @cabloy/lint is a lint config preset, not a typosquat of eslint. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-eslint-comments | AI (phantom-deps): ESLint config package; plugins are loaded by convention in config files, not direct imports. | ai | |
| typosquat | typosquat.levenshtein:pino | AI (typosquat): Scoped package @cabloy/lint is a lint config preset, not a typosquat of pino. | ai | |
| phantom-deps | phantom-dep:@eslint/json | AI (phantom-deps): ESLint config package; plugins are loaded by convention in config files, not direct imports. | ai | |
| phantom-deps | phantom-dep:@eslint/markdown | AI (phantom-deps): ESLint config package; plugins are loaded by convention in config files, not direct imports. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-vue | AI (phantom-deps): ESLint config package; plugins are loaded by convention in config files, not direct imports. | ai | |
| phantom-deps | phantom-dep:typescript-eslint | AI (phantom-deps): ESLint config package; plugins are loaded by convention in config files, not direct imports. | ai | |
| phantom-deps | phantom-dep:@e18e/eslint-plugin | AI (phantom-deps): ESLint config package; plugins are loaded by convention in config files, not direct imports. | ai | |
| phantom-deps | phantom-dep:@stylistic/eslint-plugin | AI (phantom-deps): ESLint config package; plugins are loaded by convention in config files, not direct imports. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 5.1.26 | 17 / 0 | |
| 5.1.21 | 18 / 4 | |
| 5.1.20 | 18 / 4 | |
| 5.1.19 | 18 / 4 | |
| 5.1.18 | 18 / 0 | |
| 5.1.17 | 18 / 0 | |
| 5.1.16 | 18 / 0 | |
| 5.1.15 | 18 / 0 | |
| 5.1.14 | 14 / 0 | |
| 5.1.13 | 13 / 0 | |
| 5.1.12 | 12 / 0 | |
| 5.1.11 | 11 / 0 | |
| 5.1.10 | 10 / 0 | |
| 5.1.9 | 9 / 0 | |
| 5.1.8 | 9 / 0 | |
| 5.1.7 | 9 / 0 | |
| 5.1.5 | 9 / 0 | |
| 5.1.4 | 11 / 0 | |
| 5.1.3 | 11 / 0 | |
| 5.1.2 | 11 / 0 | |
| 5.1.1 | 11 / 0 | |
| 5.0.24 | 11 / 0 | |
| 5.0.23 | 11 / 0 | |
| 5.0.22 | 11 / 0 | |
| 5.0.21 | 8 / 0 | |
| 5.0.20 | 8 / 0 | |
| 5.0.19 | 8 / 0 | |
| 5.0.18 | 8 / 0 | |
| 5.0.17 | 8 / 0 | |
| 5.0.16 | 8 / 0 | |
| 5.0.15 | 8 / 0 | |
| 5.0.14 | 8 / 0 | |
| 5.0.12 | 8 / 0 |
v5.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.