@valbuild/eslint-plugin
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; gitHead absence is cosmetic given Sigstore-backed CI publish. | ai |
Versions (showing 76 of 76)
| Version | Deps | Published |
|---|---|---|
| 0.93.0 | 0 / 5 | |
| 0.92.0 | 0 / 5 | |
| 0.91.4 | 0 / 5 | |
| 0.91.3 | 0 / 5 | |
| 0.91.2 | 0 / 5 | |
| 0.91.1 | 0 / 5 | |
| 0.91.0 | 0 / 5 | |
| 0.90.0 | 0 / 5 | |
| 0.88.0 | 0 / 5 | |
| 0.87.5 | 0 / 5 | |
| 0.87.4 | 0 / 5 | |
| 0.87.3 | 0 / 5 | |
| 0.87.2 | 0 / 5 | |
| 0.87.1 | 0 / 5 | |
| 0.87.0 | 0 / 5 | |
| 0.86.3 | 0 / 5 | |
| 0.86.2 | 0 / 5 | |
| 0.86.1 | 0 / 5 | |
| 0.86.0 | 0 / 5 | |
| 0.85.1 | 0 / 5 | |
| 0.85.0 | 0 / 5 | |
| 0.84.3 | 0 / 5 | |
| 0.84.2 | 0 / 5 | |
| 0.84.1 | 0 / 5 | |
| 0.84.0 | 0 / 5 | |
| 0.83.0 | 0 / 5 | |
| 0.82.0 | 0 / 5 | |
| 0.81.0 | 0 / 5 | |
| 0.80.0 | 0 / 5 | |
| 0.79.4 | 0 / 5 | |
| 0.79.3 | 0 / 5 | |
| 0.79.2 | 0 / 5 | |
| 0.79.1 | 0 / 5 | |
| 0.79.0 | 0 / 5 | |
| 0.78.3 | 0 / 5 | |
| 0.78.2 | 0 / 5 | |
| 0.78.1 | 0 / 5 | |
| 0.78.0 | 0 / 5 | |
| 0.77.1 | 0 / 5 | |
| 0.77.0 | 0 / 5 | |
| 0.76.1 | 0 / 5 | |
| 0.76.0 | 0 / 5 | |
| 0.75.5 | 0 / 5 | |
| 0.75.4 | 0 / 5 | |
| 0.75.3 | 0 / 5 | |
| 0.75.2 | 0 / 5 | |
| 0.75.1 | 0 / 5 | |
| 0.75.0 | 0 / 5 | |
| 0.74.0 | 0 / 5 | |
| 0.73.2 | 0 / 5 | |
| 0.73.1 | 0 / 5 | |
| 0.73.0 | 0 / 5 | |
| 0.72.4 | 0 / 5 | |
| 0.72.3 | 0 / 5 | |
| 0.72.2 | 0 / 5 | |
| 0.72.1 | 0 / 5 | |
| 0.70.0 | 0 / 5 | |
| 0.69.3 | 0 / 5 | |
| 0.69.1 | 0 / 5 | |
| 0.69.0 | 0 / 5 | |
| 0.67.2 | 0 / 5 | |
| 0.67.0 | 0 / 5 | |
| 0.66.0 | 0 / 5 | |
| 0.65.2 | 0 / 5 | |
| 0.65.0 | 0 / 5 | |
| 0.64.0 | 0 / 5 | |
| 0.63.5 | 0 / 5 | |
| 0.63.1 | 0 / 5 | |
| 0.63.0 | 0 / 5 | |
| 0.62.6 | 0 / 5 | |
| 0.62.5 | 0 / 5 | |
| 0.62.4 | 0 / 5 | |
| 0.62.3 | 0 / 5 | |
| 0.62.2 | 0 / 5 | |
| 0.62.1 | 0 / 5 | |
| 0.62.0 | 0 / 5 |
v0.78.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.78.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.78.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.78.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.77.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.77.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.67.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.67.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.66.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.65.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.65.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.64.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.63.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.63.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.63.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.