@nodeblocks/frontend-view-basic-information-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 dependency, bundled into the package; stable pattern across versions. | ai | |
| provenance | no-provenance | AI (provenance): New org package; absence of provenance is common and no other risk signals present. | ai | |
| phantom-deps | phantom-dep:@nodeblocks/frontend-base-block | AI (phantom-deps): Same-org sibling dep listed in bundleDependencies; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:type-fest | AI (phantom-deps): Type-only utility used in config/type files; not directly imported at runtime — stable false positive. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.0.6 | 2 / 19 | |
| 0.0.5 | 2 / 19 | |
| 0.0.4 | 2 / 19 | |
| 0.0.3 | 2 / 17 | |
| 0.0.2 | 2 / 17 | |
| 0.0.1 | 2 / 17 |
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.