@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, so a manually published version cannot be tied back to a reviewed commit.
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 66 of 166)
| Version | Deps | Published |
|---|---|---|
| 4.85.0 | 33 / 6 | |
| 4.84.0 | 33 / 6 | |
| 4.83.0 | 33 / 6 | |
| 4.82.3 | 33 / 6 | |
| 4.82.2 | 33 / 6 | |
| 4.82.1 | 33 / 6 | |
| 4.82.0 | 33 / 6 | |
| 4.81.5 | 33 / 6 | |
| 4.81.4 | 33 / 6 | |
| 4.81.3 | 33 / 6 | |
| 4.81.2 | 33 / 6 | |
| 4.81.1 | 33 / 6 | |
| 4.81.0 | 33 / 6 | |
| 4.80.20 | 33 / 6 | |
| 4.80.19 | 33 / 6 | |
| 4.80.18 | 33 / 6 | |
| 4.80.17 | 33 / 6 | |
| 4.80.16 | 33 / 6 | |
| 4.80.15 | 33 / 6 | |
| 4.80.14 | 33 / 6 | |
| 4.80.13 | 33 / 6 | |
| 4.80.12 | 33 / 6 | |
| 4.80.11 | 33 / 6 | |
| 4.80.10 | 33 / 6 | |
| 4.80.9 | 33 / 6 | |
| 4.80.8 | 33 / 6 | |
| 4.80.7 | 33 / 6 | |
| 4.80.6 | 33 / 6 | |
| 4.80.5 | 33 / 6 | |
| 4.80.4 | 33 / 6 | |
| 4.80.3 | 33 / 6 | |
| 4.80.2 | 33 / 6 | |
| 4.80.1 | 33 / 6 | |
| 4.80.0 | 33 / 6 | |
| 4.79.2 | 33 / 6 | |
| 4.79.1 | 33 / 6 | |
| 4.79.0 | 33 / 6 | |
| 4.78.14 | 33 / 6 | |
| 4.78.13 | 33 / 6 | |
| 4.78.12 | 33 / 6 | |
| 4.78.11 | 33 / 6 | |
| 4.78.10 | 33 / 6 | |
| 4.78.9 | 33 / 6 | |
| 4.78.8 | 33 / 6 | |
| 4.78.7 | 33 / 6 | |
| 4.78.6 | 33 / 6 | |
| 4.78.5 | 33 / 6 | |
| 4.78.4 | 33 / 6 | |
| 4.78.3 | 33 / 6 | |
| 4.78.2 | 33 / 6 | |
| 4.78.1 | 33 / 6 | |
| 4.78.0 | 33 / 6 | |
| 4.77.0 | 33 / 6 | |
| 4.76.3 | 33 / 6 | |
| 4.76.2 | 33 / 6 | |
| 4.76.1 | 33 / 6 | |
| 4.76.0 | 33 / 6 | |
| 4.75.9 | 33 / 6 | |
| 4.75.8 | 33 / 6 | |
| 4.75.7 | 33 / 6 | |
| 4.75.6 | 33 / 6 | |
| 4.75.5 | 33 / 6 | |
| 4.75.4 | 33 / 6 | |
| 4.75.3 | 33 / 6 | |
| 4.75.2 | 33 / 6 | |
| 4.75.1 | 33 / 6 |
v4.78.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.77.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.76.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.76.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.76.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.76.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.75.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.75.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.75.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.75.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.75.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.75.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.75.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.75.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.75.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.