@trapar-waves/react-mantine-tailwind
A React template integrating Mantine UI and Tailwind CSS for modern web development
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 |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): postinstall runs `husky` only — standard git hooks setup, no network fetch or arbitrary code execution. | ai | |
| phantom-deps | phantom-dep:@mantine/hooks | AI (phantom-deps): @mantine/hooks is a declared dependency used in config/template context; stable false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 4 / 26 | |
| 1.1.17 | 4 / 23 | |
| 1.1.0 | 4 / 23 | |
| 1.0.12 | 4 / 21 | |
| 1.0.11 | 4 / 17 | |
| 1.0.10 | 4 / 17 | |
| 1.0.9 | 4 / 17 | |
| 1.0.8 | 4 / 17 | |
| 1.0.7 | 4 / 17 | |
| 1.0.6 | 4 / 17 |
v1.1.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.