@washingtonpost/eslint-plugin-wpds
WPDS lint rules
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established WashPost org package with 105 versions; dormancy likely reflects org publishing workflow changes, not takeover. | ai | |
| provenance | no-provenance | AI (provenance): Established WaPo org package; lack of provenance is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 2.15.0 | 1 / 1 | |
| 2.14.0 | 1 / 1 | |
| 2.13.3 | 1 / 1 | |
| 2.13.1 | 1 / 1 | |
| 2.12.0 | 1 / 1 | |
| 2.11.1 | 1 / 1 | |
| 2.11.0 | 1 / 1 | |
| 2.10.1 | 1 / 1 | |
| 2.10.0 | 1 / 1 | |
| 2.9.0 | 1 / 1 | |
| 2.8.1 | 1 / 1 | |
| 2.8.0 | 1 / 1 | |
| 2.7.0 | 1 / 1 | |
| 2.6.0 | 1 / 1 | |
| 2.5.0 | 1 / 1 | |
| 2.4.0 | 1 / 1 | |
| 2.3.2 | 1 / 1 | |
| 2.3.1 | 1 / 1 | |
| 2.3.0 | 1 / 1 | |
| 2.2.0 | 1 / 1 | |
| 2.1.2 | 1 / 1 | |
| 2.1.1 | 1 / 1 | |
| 2.1.0 | 1 / 1 |
v2.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.