@vertexvis/eslint-config-vertexvis MIT 10 versions

@vertexvis/eslint-config-vertexvis

npm Repository Homepage

The Vertex sharable ESLint config

10

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

danschultz-vertexjdm717ci-vertexbcollennick-vertex

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:dynamic-require	AI (semgrep): Fires in patch.js that patches eslint internals; not a runtime arbitrary-module-load risk for consumers.	ai	2026/04/29
phantom-deps	phantom-dep:prettier	AI (phantom-deps): ESLint config package; deps are referenced by name in config, not imported directly — expected pattern.	ai	2026/04/29
phantom-deps	phantom-dep:eslint-config-prettier	AI (phantom-deps): Same as prettier — config-by-name pattern for ESLint shareable configs.	ai	2026/04/29
phantom-deps	phantom-dep:eslint-plugin-prettier	AI (phantom-deps): Same as prettier — config-by-name pattern for ESLint shareable configs.	ai	2026/04/29
phantom-deps	phantom-dep:eslint-plugin-simple-import-sort	AI (phantom-deps): Same as prettier — config-by-name pattern for ESLint shareable configs.	ai	2026/04/29

Versions (showing 10 of 10)

Version	Deps	Published
0.8.0	3 / 1	2026-07-01
0.7.2	4 / 1	2026-04-27
0.7.1	4 / 1	2023-09-06
0.7.0	4 / 1	2022-01-10
0.6.1	3 / 1	2021-09-22
0.6.0	3 / 1	2021-01-28
0.5.0	3 / 0	2020-09-02
0.4.2	3 / 0	2020-06-24
0.4.1	3 / 0	2020-06-08
0.4.0	3 / 0	2020-06-04

v0.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.