@snyk/fix
Snyk fix library and utility
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): CI-based publisher switch (CircleCI) for long-established Snyk package, no behavioral diff. | ai | |
| provenance | missing-githead | AI (provenance): Publish metadata gap, no behavioral change; consistent trusted Snyk publisher. | ai | |
| phantom-deps | phantom-dep:child_process | AI (phantom-deps): Node builtin declared explicitly; not malicious, just unusual pinning. | ai | |
| phantom-deps | phantom-dep:bottleneck | AI (phantom-deps): Legit utility dep used in compiled dist, not visible to source scan. | ai | |
| phantom-deps | phantom-dep:lodash.orderby | AI (phantom-deps): Well-known lodash utility, false positive on import scan. | ai | |
| phantom-deps | phantom-dep:strip-ansi | AI (phantom-deps): Likely used indirectly/transitively by CLI output formatting; common utility, low risk. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All added deps are well-known, widely-used packages typical for a CLI tool. | ai | |
| dependencies | unvetted-dep:@snyk/dep-graph | AI (dependencies): Internal Snyk sibling package; consistently used across this package's version history. | ai | |
| dependencies | unvetted-dep:@snyk/fix-poetry | AI (dependencies): Internal Snyk sibling package; consistently used across this package's version history. | ai | |
| dependencies | unvetted-dep:@snyk/fix-pipenv-pipfile | AI (dependencies): Internal Snyk sibling package; consistently used across this package's version history. | ai | |
| provenance | no-provenance | AI (provenance): Snyk's publishing pipeline consistently lacks Sigstore attestation; stable false positive for this package family. | ai |
Versions (showing 51 of 881)
| Version | Deps | Published |
|---|---|---|
| 1.1306.2 | 11 / 0 | |
| 1.1306.1 | 11 / 0 | |
| 1.1306.0 | 11 / 0 | |
| 1.1305.2 | 11 / 0 | |
| 1.1305.1 | 11 / 0 | |
| 1.1305.0 | 11 / 0 | |
| 1.1304.3 | 11 / 0 | |
| 1.1304.2 | 11 / 0 | |
| 1.1304.1 | 11 / 0 | |
| 1.1304.0 | 11 / 0 | |
| 1.1303.2 | 11 / 0 | |
| 1.1303.1 | 11 / 0 | |
| 1.1303.0 | 11 / 0 | |
| 1.1302.1 | 11 / 0 | |
| 1.1302.0 | 11 / 0 | |
| 1.1301.2 | 11 / 0 | |
| 1.1301.1 | 11 / 0 | |
| 1.1301.0 | 11 / 0 | |
| 1.1300.2 | 11 / 0 | |
| 1.1300.1 | 11 / 0 | |
| 1.1300.0 | 11 / 0 | |
| 1.1299.1 | 11 / 0 | |
| 1.1299.0 | 11 / 0 | |
| 1.1298.3 | 11 / 0 | |
| 1.1298.2 | 11 / 0 | |
| 1.1298.1 | 11 / 0 | |
| 1.1298.0 | 11 / 0 | |
| 1.1297.3 | 11 / 0 | |
| 1.1297.2 | 11 / 0 | |
| 1.1297.1 | 11 / 0 | |
| 1.1297.0 | 11 / 0 | |
| 1.1296.2 | 11 / 0 | |
| 1.1296.1 | 11 / 0 | |
| 1.1296.0 | 11 / 0 | |
| 1.1295.4 | 11 / 0 | |
| 1.1295.3 | 11 / 0 | |
| 1.1295.2 | 11 / 0 | |
| 1.1295.1 | 11 / 0 | |
| 1.1295.0 | 11 / 0 | |
| 1.1294.3 | 11 / 0 | |
| 1.1294.2 | 11 / 0 | |
| 1.1294.1 | 11 / 0 | |
| 1.1294.0 | 11 / 0 | |
| 1.1293.1 | 11 / 0 | |
| 1.1293.0 | 11 / 0 | |
| 1.1292.4 | 11 / 0 | |
| 1.1292.3 | 11 / 0 | |
| 1.1292.2 | 11 / 0 | |
| 1.1292.1 | 11 / 0 | |
| 1.1292.0 | 11 / 0 | |
| 1.1291.1 | 11 / 0 |
v1.1306.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1306.1
2 findingsThis version was published by a different npm account than previous versions on 2026-07-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1306.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-09. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1305.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1296.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1296.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1296.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1295.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1295.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1295.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1295.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1295.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1294.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1294.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1294.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1294.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1293.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1293.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1292.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1292.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1292.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1292.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1292.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1291.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.