@blocknote/shadcn
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/blocknote-shadcn.cjs | AI (source-diff): Minified vite build output, not obfuscation; stable for this package's dist. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same benign handoff to established maintainer. | ai | |
| provenance | publisher-changed | AI (provenance): Legitimate BlockNote maintainer transition; publisher has strong track record. | ai | |
| phantom-deps | phantom-dep:tailwindcss | AI (phantom-deps): CSS framework dep for shadcn styling; not imported in runtime code. | ai | |
| phantom-deps | phantom-dep:postcss | AI (phantom-deps): Build tooling dep; not imported in runtime code. | ai | |
| phantom-deps | phantom-dep:tailwindcss-animate | AI (phantom-deps): Tailwind plugin; config-only usage expected in shadcn package. | ai | |
| phantom-deps | phantom-dep:@hookform/resolvers | AI (phantom-deps): Referenced in config files only; consistent with build tooling pattern for this package. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is used in config/form validation context; not directly imported in main source but legitimately declared. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-avatar | AI (dependencies): Radix UI primitive; consistent with other @radix-ui/* deps already used throughout this package. | ai | |
| phantom-deps | phantom-dep:autoprefixer | AI (phantom-deps): autoprefixer is a build-time CSS tool referenced in config; not a runtime import — stable false positive for this package. | ai |
Versions (showing 51 of 93)
| Version | Deps | Published |
|---|---|---|
| 0.52.1 | 16 / 12 | |
| 0.52.0 | 16 / 12 | |
| 0.51.4 | 17 / 14 | |
| 0.51.3 | 17 / 14 | |
| 0.51.2 | 17 / 14 | |
| 0.51.1 | 17 / 14 | |
| 0.51.0 | 17 / 14 | |
| 0.50.0 | 17 / 14 | |
| 0.49.0 | 17 / 14 | |
| 0.48.1 | 17 / 14 | |
| 0.48.0 | 17 / 14 | |
| 0.47.3 | 17 / 14 | |
| 0.47.2 | 17 / 14 | |
| 0.47.1 | 17 / 14 | |
| 0.47.0 | 17 / 14 | |
| 0.46.2 | 17 / 14 | |
| 0.46.1 | 17 / 14 | |
| 0.46.0 | 17 / 14 | |
| 0.45.0 | 18 / 14 | |
| 0.44.2 | 18 / 14 | |
| 0.44.1 | 18 / 14 | |
| 0.44.0 | 18 / 14 | |
| 0.43.0 | 18 / 14 | |
| 0.42.3 | 18 / 14 | |
| 0.42.2 | 18 / 14 | |
| 0.42.1 | 18 / 14 | |
| 0.42.0 | 18 / 14 | |
| 0.41.1 | 19 / 14 | |
| 0.41.0 | 19 / 14 | |
| 0.40.0 | 19 / 14 | |
| 0.39.2 | 19 / 14 | |
| 0.39.1 | 19 / 14 | |
| 0.39.0 | 19 / 14 | |
| 0.38.0 | 19 / 14 | |
| 0.37.0 | 19 / 14 | |
| 0.36.1 | 22 / 14 | |
| 0.36.0 | 22 / 14 | |
| 0.35.0 | 22 / 14 | |
| 0.34.0 | 22 / 14 | |
| 0.33.0 | 22 / 12 | |
| 0.32.0 | 22 / 12 | |
| 0.31.3 | 22 / 12 | |
| 0.31.2 | 22 / 12 | |
| 0.31.1 | 22 / 12 | |
| 0.31.0 | 22 / 12 | |
| 0.30.1 | 22 / 12 | |
| 0.30.0 | 22 / 12 | |
| 0.27.2 | 22 / 13 | |
| 0.25.0 | 22 / 13 | |
| 0.24.2 | 21 / 13 | |
| 0.24.1 | 21 / 13 |
v0.52.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.52.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.27.2
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nperez0111.
Newly 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.
This version was published by a different npm account (nperez0111) than the most recent previously approved version (matthewlipski) on 2025-04-05, but nperez0111 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.25.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nperez0111) than the most recent previously approved version (matthewlipski) on 2025-03-04, but nperez0111 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (matthewlipski) than the most recent previously approved version (yousefed) on 2025-02-20, but matthewlipski is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.