← Home

eslint-plugin-vuejs-accessibility

npm Repository Homepage
10
Versions
—
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

kddeiszvhoyer

Keywords

eslinteslint-plugina11yaccessibilityvuevuejs

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff large-new-source-files AI (source-diff): Growth explained by generated .d.ts declaration files, not injected payload. ai
source-diff source-size-tripled AI (source-diff): Size increase matches new TS build/declaration output, benign. ai
publish-pattern dormant-publish AI (publish-pattern): Long-running trusted plugin with irregular but consistent release cadence. ai
phantom-deps phantom-dep:emoji-regex AI (phantom-deps): Likely used in compiled dist output; no install scripts or other risk signals. ai

Versions (showing 10 of 10)

Version Deps Published
2.5.0 2 / 20
2.4.2 2 / 20
2.4.1 3 / 20
2.4.0 3 / 20
2.3.1 3 / 20
2.3.0 3 / 20
2.2.1 3 / 17
2.2.0 3 / 17
2.1.0 3 / 16
2.0.0 3 / 15

v2.4.1

1 finding
LOW No provenance attestation provenance

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

v2.4.0

1 finding
LOW No provenance attestation provenance

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

v2.3.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.

v2.3.0

1 finding
LOW No provenance attestation provenance

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

v2.2.1

1 finding
LOW No provenance attestation provenance

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

v2.2.0

1 finding
LOW No provenance attestation provenance

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

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

v2.0.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.