@knapsack/tiptap-utils
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@knapsack/utils | AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic fires on monorepo packages that re-export or conditionally import. | ai | |
| phantom-deps | phantom-dep:@tiptap/extension-link | AI (phantom-deps): Referenced in config files per finding; stable false positive for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo utility package with empty description string; not a malware indicator here. | ai |
Versions (showing 51 of 107)
| Version | Deps | Published |
|---|---|---|
| 4.93.0 | 24 / 6 | |
| 4.92.24 | 24 / 6 | |
| 4.92.23 | 24 / 6 | |
| 4.92.22 | 24 / 6 | |
| 4.92.21 | 24 / 6 | |
| 4.92.20 | 24 / 6 | |
| 4.92.19 | 24 / 6 | |
| 4.92.18 | 24 / 6 | |
| 4.92.17 | 24 / 6 | |
| 4.92.16 | 24 / 6 | |
| 4.92.15 | 24 / 6 | |
| 4.92.14 | 24 / 6 | |
| 4.92.13 | 24 / 6 | |
| 4.92.12 | 24 / 6 | |
| 4.92.11 | 24 / 6 | |
| 4.92.10 | 24 / 6 | |
| 4.92.9 | 24 / 6 | |
| 4.92.8 | 24 / 6 | |
| 4.92.7 | 24 / 6 | |
| 4.92.6 | 24 / 6 | |
| 4.92.5 | 24 / 6 | |
| 4.92.4 | 24 / 6 | |
| 4.92.3 | 24 / 6 | |
| 4.92.2 | 24 / 6 | |
| 4.92.1 | 24 / 6 | |
| 4.92.0 | 24 / 6 | |
| 4.91.0 | 24 / 6 | |
| 4.90.0 | 24 / 6 | |
| 4.89.13 | 24 / 6 | |
| 4.89.12 | 24 / 6 | |
| 4.89.11 | 24 / 6 | |
| 4.89.10 | 24 / 6 | |
| 4.89.9 | 33 / 6 | |
| 4.89.8 | 33 / 6 | |
| 4.89.7 | 33 / 6 | |
| 4.89.6 | 33 / 6 | |
| 4.89.5 | 33 / 6 | |
| 4.89.3 | 33 / 6 | |
| 4.89.2 | 33 / 6 | |
| 4.89.1 | 33 / 6 | |
| 4.89.0 | 33 / 6 | |
| 4.88.0 | 33 / 6 | |
| 4.87.9 | 33 / 6 | |
| 4.87.8 | 33 / 6 | |
| 4.87.7 | 33 / 6 | |
| 4.87.6 | 33 / 6 | |
| 4.87.5 | 33 / 6 | |
| 4.87.4 | 33 / 6 | |
| 4.87.3 | 33 / 6 | |
| 4.87.2 | 33 / 6 | |
| 4.87.1 | 33 / 6 |
v4.93.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.22
1 findingPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.91.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.90.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.88.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.87.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.87.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.