@knapsack/source-conflicts-adapter
Source conflicts ContextSrcAdapter — detect and compare entity conflicts across sources.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Monorepo package; provenance not critical for internal org dependencies. | ai | |
| license | copyleft-license:GPL-2.0-or-later | AI (license): License declared transparently; org owns both this and dependent packages. | ai | |
| dependencies | unvetted-dep:mdast-util-to-string | AI (dependencies): mdast-util-to-string is a well-known, widely-used remark/unified ecosystem package; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@knapsack/utils | AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic unreliable for monorepo internal packages. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 4.93.0 | 15 / 6 | |
| 4.92.24 | 15 / 7 | |
| 4.92.23 | 15 / 7 | |
| 4.92.21 | 15 / 7 | |
| 4.92.20 | 15 / 7 | |
| 4.92.19 | 15 / 7 | |
| 4.92.2 | 15 / 7 | |
| 4.92.1 | 15 / 7 | |
| 4.92.0 | 15 / 7 | |
| 4.89.13 | 15 / 7 | |
| 4.89.12 | 15 / 7 | |
| 4.89.10 | 14 / 7 |
v4.93.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.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.
v4.89.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.89.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.89.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.