← Home

@voicenter-team/eslint-config-ts

npm Repository Homepage

Shared eslint config

4
Versions
ISC
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

tzachishreganizeev.olikernitzan-npmbohdan.du

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): New maintainers are within the same VoicenterTeam org; consistent with internal team rotation. ai
maintainer-change maintainer-removed AI (maintainer-change): Removals paired with org-internal additions; no evidence of hostile takeover. ai
publish-pattern new-deps-added AI (publish-pattern): All 4 new deps are canonical ESLint v9/v10 ecosystem packages; expected for a major version bump. ai

Versions (showing 4 of 4)

Version Deps Published
2.0.1 4 / 2
2.0.0 4 / 2
1.0.25 0 / 4
1.0.24 0 / 4

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.0

1 finding
LOW No provenance attestation provenance

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

v1.0.25

1 finding
LOW No provenance attestation provenance

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

v1.0.24

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.