← Home

@botonic/eslint-config

npm
16
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

ahubstreericmarcoskhaeshahmrabatoraventosalbert_gomarizteam.platform

Keywords

bot-frameworkeslinteslintconfigjavascripttypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:eslint-plugin-jest AI (phantom-deps): ESLint config packages declare plugins as deps but reference them in config, not code. ai
phantom-deps phantom-dep:eslint-plugin-node AI (phantom-deps): ESLint config packages declare plugins as deps but reference them in config, not code. ai
phantom-deps phantom-dep:eslint-plugin-react AI (phantom-deps): ESLint config packages declare plugins as deps but reference them in config, not code. ai
phantom-deps phantom-dep:eslint-plugin-import AI (phantom-deps): ESLint config packages declare plugins as deps but reference them in config, not code. ai
phantom-deps phantom-dep:eslint-plugin-no-null AI (phantom-deps): ESLint config packages declare plugins as deps but reference them in config, not code. ai
phantom-deps phantom-dep:eslint-plugin-promise AI (phantom-deps): ESLint config packages declare plugins as deps but reference them in config, not code. ai
phantom-deps phantom-dep:eslint-plugin-prettier AI (phantom-deps): ESLint config packages declare plugins as deps but reference them in config, not code. ai
phantom-deps phantom-dep:eslint-plugin-filenames AI (phantom-deps): ESLint config packages declare plugins as deps but reference them in config, not code. ai
phantom-deps phantom-dep:@typescript-eslint/parser AI (phantom-deps): ESLint config packages declare plugins as deps but reference them in config, not code. ai
phantom-deps phantom-dep:eslint-plugin-react-hooks AI (phantom-deps): ESLint config packages declare plugins as deps but reference them in config, not code. ai
phantom-deps phantom-dep:@typescript-eslint/eslint-plugin AI (phantom-deps): ESLint config packages declare plugins as deps but reference them in config, not code. ai
phantom-deps phantom-dep:eslint-plugin-simple-import-sort AI (phantom-deps): ESLint config packages declare plugins as deps but reference them in config, not code. ai

Versions (showing 16 of 16)

Version Deps Published
0.49.0 12 / 0
0.48.0 12 / 0
0.47.0 12 / 0
0.46.0 12 / 0
0.45.0 12 / 0
0.44.0 12 / 0
0.43.0 12 / 0
0.42.0 12 / 0
0.41.0 12 / 0
0.40.0 12 / 0
0.39.0 12 / 0
0.38.0 12 / 0
0.37.0 12 / 0
0.36.0 12 / 0
0.35.1 12 / 0
0.35.0 12 / 0

v0.49.0

1 finding
LOW No provenance attestation provenance

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

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

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

v0.46.0

1 finding
LOW No provenance attestation provenance

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

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

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

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

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

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

v0.40.0

1 finding
LOW No provenance attestation provenance

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

v0.39.0

1 finding
LOW No provenance attestation provenance

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

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

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

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

v0.35.1

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.

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