@swissquote/crafty-preset-eslint
<table> <tr><th>Commands</th><td>
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@swissquote/rollup-plugin-eslint | AI (dependencies): First-party org package replacing prior rollup-plugin-eslint dep. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Same-org rename, not a novel external dependency. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads a fixed subpath of eslintPath for module resolver patching; not arbitrary user-controlled input. | ai | |
| phantom-deps | phantom-dep:@swissquote/eslint-plugin-swissquote | AI (phantom-deps): Same-org monorepo sibling; declared as a dependency and used transitively, not a phantom risk. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.30.2 | 6 / 4 | |
| 1.30.1 | 6 / 4 | |
| 1.30.0 | 6 / 4 | |
| 1.29.0 | 6 / 4 | |
| 1.28.1 | 6 / 2 | |
| 1.27.0 | 6 / 2 | |
| 1.26.0 | 6 / 2 | |
| 1.13.2 | 9 / 0 | |
| 1.13.0 | 9 / 0 | |
| 1.12.0 | 9 / 0 | |
| 1.11.1 | 9 / 0 | |
| 1.11.0 | 9 / 0 | |
| 1.10.0 | 9 / 0 | |
| 1.9.1 | 9 / 0 | |
| 1.9.0 | 9 / 0 | |
| 1.8.0 | 9 / 0 | |
| 1.7.3 | 9 / 0 | |
| 1.7.2 | 9 / 0 | |
| 1.7.1 | 9 / 0 | |
| 1.7.0 | 9 / 0 |
v1.30.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.