@hs-web-team/eslint-config-node
HubSpot Marketing WebTeam shared configurations for ESLint, Prettier, Stylelint, and Cypress
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:axe-core | AI (phantom-deps): axe-core is referenced in cypress config files, not directly imported; standard for eslint/cypress config packages. | ai | |
| phantom-deps | phantom-dep:esbuild | AI (phantom-deps): Binary dep used by cypress-esbuild-preprocessor; implicit runtime dep. | ai | |
| phantom-deps | phantom-dep:prettier | AI (phantom-deps): ESLint config package; prettier loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@eslint/eslintrc | AI (phantom-deps): Framework-scoped package loaded by ESLint convention, not direct import. | ai | |
| phantom-deps | phantom-dep:jiti | AI (phantom-deps): ESLint config package; tools declared as deps but loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:eslint-formatter-checkstyle | AI (phantom-deps): ESLint config package; formatter referenced in config, not directly imported. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/eslint-plugin | AI (phantom-deps): ESLint config package; plugin referenced in config, not directly imported. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/parser | AI (phantom-deps): ESLint config package; parser referenced in config, not directly imported. | ai | |
| phantom-deps | phantom-dep:eslint | AI (phantom-deps): ESLint config package; eslint is a peer/runtime dep loaded by convention. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.3.2 | 18 / 0 | |
| 3.3.0 | 18 / 0 | |
| 3.2.0 | 16 / 0 | |
| 3.1.3 | 13 / 0 | |
| 3.1.2 | 13 / 0 | |
| 3.1.1 | 13 / 0 | |
| 3.0.0 | 10 / 0 |
v3.3.2
2 findingsThis version was published by a different npm account than previous versions on 2026-05-27. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.3.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-27. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.