@blocknote/xl-ai
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/client-BPNTLm1-.cjs | AI (source-diff): Minified bundler output (long lines), not real obfuscation; no malicious behavior present. | ai | |
| source-diff | obfuscated-file:dist/client-CUJscXD0.cjs | AI (source-diff): Minified bundler output, not true obfuscation; matches package's stated AI/editor functionality. | ai | |
| source-diff | obfuscated-file:dist/client-DrruPiJu.cjs | AI (source-diff): Minified bundler output (esbuild-style), not true obfuscation; matches legitimate library code. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): lodash.merge is a well-known utility, used directly in the diffed source. | ai | |
| phantom-deps | phantom-dep:remark-stringify | AI (phantom-deps): Runtime dep used in bundled output; phantom-dep heuristic misfires for this package. | ai | |
| phantom-deps | phantom-dep:unified | AI (phantom-deps): Monorepo package; unified is a runtime dep used in bundled output, not directly imported at source level. | ai | |
| phantom-deps | phantom-dep:@blocknote/mantine | AI (phantom-deps): Same-org sibling package; phantom-dep heuristic is a known false positive for monorepo cross-package deps. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Declared as peer dep and runtime dep; phantom-dep heuristic fires incorrectly for peer deps in monorepos. | ai | |
| phantom-deps | phantom-dep:@tiptap/core | AI (phantom-deps): Transitive/bundled usage in a ProseMirror/Tiptap-based editor; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:remark-parse | AI (phantom-deps): Runtime dep used in bundled output; phantom-dep heuristic misfires for this package. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.51.4 | 21 / 30 | |
| 0.51.3 | 21 / 30 | |
| 0.51.2 | 21 / 30 | |
| 0.51.1 | 21 / 30 | |
| 0.51.0 | 21 / 30 | |
| 0.50.0 | 24 / 29 | |
| 0.49.0 | 24 / 29 | |
| 0.48.1 | 24 / 29 | |
| 0.48.0 | 24 / 29 | |
| 0.47.3 | 24 / 29 | |
| 0.47.2 | 24 / 29 | |
| 0.47.1 | 24 / 29 | |
| 0.47.0 | 24 / 29 | |
| 0.46.2 | 24 / 29 | |
| 0.46.1 | 24 / 29 | |
| 0.46.0 | 24 / 29 | |
| 0.45.0 | 24 / 29 | |
| 0.44.2 | 24 / 29 | |
| 0.44.1 | 24 / 29 | |
| 0.44.0 | 24 / 29 | |
| 0.43.0 | 23 / 28 |
v0.47.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.47.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.47.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.47.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.46.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.46.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.46.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.45.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.44.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.44.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.44.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.43.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.