← Home

eslint-plugin-unused-imports

Report and remove unused es6 modules

30
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

antfusweepline

Keywords

eslinteslintplugineslint-pluginimportunusedmodulesautofix

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Expected when transitioning to GitHub Actions publishing; SLSA provenance attestation compensates. ai
provenance publisher-changed AI (provenance): Transition from antfu to GitHub Actions CI/CD publishing with SLSA provenance; legitimate automation change. ai
bogus-package bogus-package AI (bogus-package): antfu (Anthony Fu) is a prominent OSS maintainer (Vue/Vite core); spam flag is a false positive. ai

Versions (showing 30 of 30)

Version Deps Published
4.4.1 0 / 17
4.3.0 0 / 17
4.2.0 0 / 17
4.1.4 0 / 16
4.1.3 0 / 16
4.1.2 0 / 16
4.1.1 0 / 16
4.1.0 0 / 16
4.0.1 1 / 6
4.0.0 1 / 6
3.2.0 1 / 6
3.1.0 1 / 6
3.0.0 1 / 4
2.0.0 1 / 4
1.1.5 1 / 5
1.1.4 1 / 5
1.1.3 1 / 5
1.1.2 1 / 6
1.1.1 1 / 6
1.1.0 1 / 6
1.0.3 2 / 6
1.0.2 1 / 6
1.0.1 5 / 3
1.0.0 5 / 3
0.1.3 5 / 4
0.1.2 5 / 4
0.1.1 5 / 4
0.1.0 5 / 4
0.0.3 3 / 1
0.0.2 1 / 3

v4.4.1

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

HIGH Publisher changed: antfu → GitHub Actions (on 2026-02-09) provenance

This version was published by a different npm account than previous versions on 2026-02-09. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v4.3.0

2 findings
LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: antfu.

v4.2.0

1 finding
LOW No provenance attestation provenance

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

v4.1.4

2 findings
LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: antfu.

v4.1.3

2 findings
LOW No provenance attestation provenance

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

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: antfu.

v4.1.2

1 finding
LOW No provenance attestation provenance

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

v4.1.1

1 finding
LOW No provenance attestation provenance

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

v4.1.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: sweepline → antfu (on 2024-08-08) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2024-08-08. This could indicate a legitimate maintainer transition or an account compromise.

v4.0.1

1 finding
LOW No provenance attestation provenance

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

v4.0.0

1 finding
LOW No provenance attestation provenance

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

v3.2.0

1 finding
LOW No provenance attestation provenance

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

v3.1.0

1 finding
LOW No provenance attestation provenance

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

v3.0.0

1 finding
LOW No provenance attestation provenance

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