@blocknote/mantine
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-mantine.cjs | AI (source-diff): Minified Vite build output, not obfuscation; stable for this package's dist. | ai | |
| provenance | missing-githead | AI (provenance): gitHead dropped when moving to CI/CD trusted-publisher flow with SLSA attestation; benign environment change. | ai | |
| source-diff | obfuscated-file:dist/blocknote-mantine.cjs | AI (source-diff): Minified Vite/rollup build output with readable identifiers; no obfuscation signature or malicious behavior. | ai | |
| dependencies | unvetted-dep:use-prefers-color-scheme | AI (dependencies): Small, legitimate utility dep used for theme detection; no malicious history. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Peer dependency used via config/build tooling, not a direct import concern. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI/CD publishing with SLSA provenance; legitimate automation change. | ai | |
| phantom-deps | phantom-dep:@mantine/utils | AI (phantom-deps): Declared dep referenced in config only; stable pattern for this package. | ai |
Versions (showing 99 of 99)
| Version | Deps | Published |
|---|---|---|
| 0.52.0 | 2 / 11 | |
| 0.51.4 | 3 / 12 | |
| 0.51.3 | 3 / 12 | |
| 0.51.2 | 3 / 12 | |
| 0.51.1 | 3 / 12 | |
| 0.51.0 | 3 / 12 | |
| 0.50.0 | 3 / 12 | |
| 0.49.0 | 3 / 12 | |
| 0.48.1 | 3 / 12 | |
| 0.48.0 | 3 / 12 | |
| 0.47.3 | 3 / 12 | |
| 0.47.2 | 3 / 12 | |
| 0.47.1 | 3 / 12 | |
| 0.47.0 | 3 / 12 | |
| 0.46.2 | 3 / 12 | |
| 0.46.1 | 3 / 12 | |
| 0.46.0 | 3 / 12 | |
| 0.45.0 | 3 / 12 | |
| 0.44.2 | 3 / 12 | |
| 0.44.1 | 3 / 12 | |
| 0.44.0 | 3 / 12 | |
| 0.43.0 | 3 / 12 | |
| 0.42.3 | 3 / 12 | |
| 0.42.2 | 3 / 12 | |
| 0.42.1 | 3 / 12 | |
| 0.42.0 | 3 / 12 | |
| 0.41.1 | 3 / 12 | |
| 0.41.0 | 3 / 12 | |
| 0.40.0 | 3 / 12 | |
| 0.39.2 | 6 / 12 | |
| 0.39.1 | 6 / 12 | |
| 0.39.0 | 6 / 12 | |
| 0.38.0 | 6 / 12 | |
| 0.37.0 | 6 / 12 | |
| 0.36.1 | 6 / 12 | |
| 0.36.0 | 6 / 12 | |
| 0.35.0 | 6 / 12 | |
| 0.34.0 | 6 / 12 | |
| 0.33.0 | 6 / 10 | |
| 0.32.0 | 6 / 10 | |
| 0.31.3 | 6 / 10 | |
| 0.31.2 | 6 / 10 | |
| 0.31.1 | 6 / 10 | |
| 0.31.0 | 6 / 10 | |
| 0.30.1 | 6 / 10 | |
| 0.30.0 | 6 / 10 | |
| 0.29.1 | 6 / 11 | |
| 0.29.0 | 6 / 11 | |
| 0.28.0 | 6 / 11 | |
| 0.27.2 | 6 / 11 | |
| 0.27.0 | 6 / 11 | |
| 0.26.0 | 6 / 11 | |
| 0.25.2 | 6 / 11 | |
| 0.25.1 | 6 / 11 | |
| 0.25.0 | 6 / 11 | |
| 0.24.2 | 6 / 11 | |
| 0.24.1 | 6 / 11 | |
| 0.24.0 | 6 / 11 | |
| 0.23.6 | 6 / 11 | |
| 0.23.5 | 6 / 11 | |
| 0.23.4 | 6 / 11 | |
| 0.23.3 | 6 / 11 | |
| 0.23.2 | 6 / 11 | |
| 0.23.1 | 6 / 11 | |
| 0.23.0 | 6 / 11 | |
| 0.22.0 | 6 / 11 | |
| 0.21.0 | 6 / 11 | |
| 0.20.0 | 6 / 11 | |
| 0.19.2 | 6 / 11 | |
| 0.19.1 | 6 / 11 | |
| 0.19.0 | 6 / 11 | |
| 0.18.1 | 6 / 11 | |
| 0.18.0 | 6 / 11 | |
| 0.17.1 | 8 / 11 | |
| 0.17.0 | 8 / 11 | |
| 0.16.0 | 8 / 11 | |
| 0.15.11 | 8 / 11 | |
| 0.15.10 | 8 / 11 | |
| 0.15.9 | 8 / 11 | |
| 0.15.7 | 8 / 11 | |
| 0.15.6 | 8 / 11 | |
| 0.15.5 | 8 / 11 | |
| 0.15.4 | 8 / 11 | |
| 0.15.3 | 8 / 11 | |
| 0.15.2 | 8 / 11 | |
| 0.15.0 | 8 / 11 | |
| 0.14.6 | 8 / 11 | |
| 0.14.5 | 8 / 11 | |
| 0.14.4 | 8 / 11 | |
| 0.14.3 | 9 / 11 | |
| 0.14.2 | 9 / 11 | |
| 0.14.1 | 9 / 11 | |
| 0.14.0 | 9 / 11 | |
| 0.13.5 | 9 / 11 | |
| 0.13.4 | 9 / 11 | |
| 0.13.3 | 9 / 11 | |
| 0.13.2 | 9 / 11 | |
| 0.13.1 | 9 / 11 | |
| 0.13.0 | 9 / 11 |
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.29.1
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-17, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v0.29.0
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-17, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v0.28.0
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-07, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
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 it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v0.27.0
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.
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-04-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.26.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
v0.25.2
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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-13, 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.1
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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-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.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.6
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 (yousefed) than the most recent previously approved version (nperez0111) on 2025-02-12, but yousefed 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.23.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-02-10. This could indicate a legitimate maintainer transition or an account compromise.
v0.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.2
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 2024-11-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.
v0.19.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 2024-11-15, 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.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.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 (yousefed) than the most recent previously approved version (matthewlipski) on 2024-10-18, but yousefed 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.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
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 2024-08-08, 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.
v0.15.3
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 (yousefed) than the most recent previously approved version (matthewlipski) on 2024-07-18, but yousefed 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.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
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 2024-07-15, 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.
v0.14.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.5
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 (yousefed) than the most recent previously approved version (matthewlipski) on 2024-07-03, but yousefed 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.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.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 2024-06-13, 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.
v0.14.0
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 2024-06-06, 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.
v0.13.5
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 (yousefed) than the most recent previously approved version (matthewlipski) on 2024-06-02, but yousefed 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.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.