@inkset/core
Core parsing, measurement, layout, and streaming pipeline for Inkset.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @inkset/core is a markdown/layout library with no relation to cors; Levenshtein match is coincidental. | ai | |
| phantom-deps | phantom-dep:marked | AI (phantom-deps): marked is a declared runtime dep in a markdown pipeline; phantom-dep heuristic likely misses indirect/re-export usage. | ai | |
| phantom-deps | phantom-dep:rehype-sanitize | AI (phantom-deps): rehype-sanitize is a declared runtime dep in a remark/rehype pipeline; phantom-dep heuristic likely misses indirect usage. | ai | |
| phantom-deps | phantom-dep:hast-util-to-jsx-runtime | AI (phantom-deps): hast-util-to-jsx-runtime is a declared runtime dep in a hast/JSX pipeline; phantom-dep heuristic likely misses indirect usage. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.1.5 | 10 / 4 | |
| 0.1.4 | 10 / 4 | |
| 0.1.3 | 10 / 4 | |
| 0.1.2 | 10 / 4 | |
| 0.1.1 | 10 / 4 | |
| 0.1.0 | 10 / 4 |
v0.1.4
2 findingsPackage name '@inkset/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
2 findingsPackage name '@inkset/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
2 findingsPackage name '@inkset/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
2 findingsPackage name '@inkset/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
2 findingsPackage name '@inkset/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.