@vertexvis/eslint-config-vertexvis-typescript MIT 11 versions

@vertexvis/eslint-config-vertexvis-typescript

npm Repository Homepage

The Vertex sharable ESLint config for TypeScript.

11

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
phantom-deps	phantom-dep:eslint-config-prettier	AI (phantom-deps): ESLint config packages reference plugins/configs by name in config objects, not via import — phantom-dep is a stable false positive here.	ai	2026/04/29
phantom-deps	phantom-dep:eslint-plugin-prettier	AI (phantom-deps): Same ESLint config pattern; referenced by name in config, not imported directly.	ai	2026/04/29
phantom-deps	phantom-dep:@typescript-eslint/parser	AI (phantom-deps): ESLint parser is referenced by string name in config, not imported — stable false positive for ESLint config packages.	ai	2026/04/29
phantom-deps	phantom-dep:@typescript-eslint/eslint-plugin	AI (phantom-deps): ESLint plugin referenced by name in config object, not imported — stable false positive for ESLint config packages.	ai	2026/04/29

Versions (showing 11 of 11)

Version	Deps	Published
0.6.0	4 / 2	2026-07-01
0.5.2	5 / 2	2026-04-27
0.5.1	5 / 2	2023-09-06
0.5.0	5 / 2	2022-01-10
0.4.1	5 / 2	2021-09-22
0.4.0	5 / 2	2021-01-28
0.3.0	5 / 0	2020-09-02
0.2.3	5 / 0	2020-08-06
0.2.2	5 / 0	2020-06-24
0.2.1	5 / 0	2020-06-08
0.2.0	5 / 0	2020-06-04

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.1

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.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. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.3

1 finding

LOW No provenance attestation provenance

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

v0.2.2

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.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.