vue-eslint-parser
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from maintainer to GitHub Actions CI/CD with SLSA provenance; legitimate automation change. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Mature, widely-used package resuming activity via CI/CD with provenance attestation. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): loadParser() is the documented mechanism for loading user-configured ESLint parsers; stable and intentional across all versions. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 10.4.1 | 6 / 30 | |
| 10.4.0 | 6 / 29 | |
| 10.3.0 | 6 / 29 | |
| 10.2.0 | 6 / 40 | |
| 10.1.4 | 7 / 41 |
v10.4.1
2 findingsThis version was published by a different npm account than previous versions on 2026-06-02. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.