@nodeblocks/frontend-view-user-block
Welcome to the Nodeblocks Frontend Starter Kit! 🎉 This kit is designed to make building frontend libraries in React super easy, helping you streamline your development workflow with minimal fuss. Let's dive in! 🤿
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@nodeblocks/frontend-base-block | AI (dependencies): Same-org sibling dep, bundled into the package; not a third-party supply chain risk. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm); no other risk signals present for this package. | ai | |
| phantom-deps | phantom-dep:@nodeblocks/frontend-base-block | AI (phantom-deps): Listed in bundleDependencies; not directly imported at source level is expected for bundled deps. | ai | |
| phantom-deps | phantom-dep:type-fest | AI (phantom-deps): type-fest is a type-only utility; used in config/type declarations, not runtime imports — stable false positive for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.0.5 | 2 / 19 | |
| 0.0.4 | 2 / 19 | |
| 0.0.3 | 2 / 19 | |
| 0.0.2 | 2 / 17 | |
| 0.0.1 | 2 / 17 |
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.