@voicenter-team/eslint-config-vue
Shared vue eslint config
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@voicenter-team/eslint-config-ts | AI (phantom-deps): Config-only package re-exports sibling; no direct import expected by design. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.0.0 | 3 / 2 | |
| 1.0.26 | 1 / 6 | |
| 1.0.25 | 1 / 6 | |
| 1.0.24 | 1 / 6 | |
| 1.0.23 | 1 / 6 | |
| 1.0.21 | 1 / 6 | |
| 1.0.20 | 1 / 6 |
v1.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.