@vue-storefront/eslint-config-integrations
> Common eslint configuration for Alokai Integrations
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:eslint | AI (phantom-deps): ESLint config packages reference ESLint in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:prettier | AI (phantom-deps): Prettier referenced in ESLint config, not directly imported in code. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-import | AI (phantom-deps): ESLint plugins referenced in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:eslint-config-prettier | AI (phantom-deps): ESLint config referenced in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-prettier | AI (phantom-deps): ESLint plugin referenced in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/parser | AI (phantom-deps): TypeScript parser referenced in ESLint config, not code imports. | ai | |
| phantom-deps | phantom-dep:eslint-config-airbnb-base | AI (phantom-deps): ESLint config referenced in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/eslint-plugin | AI (phantom-deps): TypeScript ESLint plugin referenced in config, not code imports. | ai | |
| phantom-deps | phantom-dep:eslint-import-resolver-typescript | AI (phantom-deps): ESLint resolver referenced in config files, not code imports. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.1.0 | 9 / 0 | |
| 1.0.4 | 8 / 0 | |
| 1.0.3 | 8 / 0 | |
| 1.0.2 | 8 / 0 | |
| 1.0.1 | 8 / 0 | |
| 1.0.0 | 8 / 0 |
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.