@knapsack/adapter-core
Core types, interfaces, and logging for ContextSrcAdapters
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): All 7 new deps are established remark/unified ecosystem packages; addition is consistent with MDX parsing feature work. | ai | |
| license | copyleft-license:GPL-2.0-or-later | AI (license): GPL-2.0-or-later is intentional; consistent across all versions of this package. | ai | |
| dependencies | unvetted-dep:mdast-util-to-string | AI (dependencies): mdast-util-to-string is a well-known remark/unified ecosystem utility; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo publisher; no provenance is consistent across all 425 versions. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 4.93.0 | 9 / 5 | |
| 4.92.24 | 9 / 5 | |
| 4.92.23 | 9 / 5 | |
| 4.92.22 | 9 / 5 | |
| 4.92.21 | 9 / 5 | |
| 4.92.20 | 9 / 5 | |
| 4.92.19 | 9 / 5 | |
| 4.92.18 | 9 / 5 | |
| 4.92.17 | 9 / 5 | |
| 4.92.16 | 9 / 5 | |
| 4.92.15 | 9 / 5 | |
| 4.92.14 | 2 / 5 | |
| 4.92.13 | 2 / 5 | |
| 4.92.12 | 2 / 5 | |
| 4.92.11 | 2 / 5 | |
| 4.92.10 | 2 / 5 | |
| 4.92.9 | 2 / 5 | |
| 4.92.8 | 2 / 5 | |
| 4.92.7 | 2 / 5 | |
| 4.92.6 | 2 / 5 | |
| 4.92.5 | 2 / 5 | |
| 4.92.4 | 2 / 5 | |
| 4.92.3 | 2 / 5 | |
| 4.92.2 | 2 / 5 | |
| 4.92.1 | 1 / 5 | |
| 4.92.0 | 1 / 5 | |
| 4.91.0 | 1 / 5 | |
| 4.90.0 | 1 / 5 | |
| 4.89.13 | 1 / 5 | |
| 4.89.12 | 1 / 5 | |
| 4.89.11 | 1 / 5 | |
| 4.89.10 | 1 / 5 | |
| 4.89.9 | 1 / 5 | |
| 4.89.8 | 1 / 5 |
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.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.20
1 finding[Accepted risk] Package 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. Consider requesting the maintainer enable provenance via CI/CD.
v4.91.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.90.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.