@bolttech/frontend-foundations
[](https://bolttech.io)
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Internal sort-template stringify pattern, not user input driven. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Generic base64 helper in bundled output, no malicious use found. | ai | |
| phantom-deps | phantom-dep:sanitize-html | AI (phantom-deps): Used via config, consistent with sanitization library purpose. | ai | |
| phantom-deps | phantom-dep:@storybook/addon-viewport | AI (phantom-deps): Storybook addon typically referenced via config, not import. | ai | |
| provenance | no-provenance | AI (provenance): Established package with clean history; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.12.3 | 6 / 0 | |
| 0.12.2 | 6 / 0 | |
| 0.12.0 | 6 / 0 | |
| 0.11.0 | 6 / 0 | |
| 0.10.2 | 6 / 0 | |
| 0.10.1 | 6 / 0 | |
| 0.10.0 | 6 / 0 | |
| 0.9.4 | 6 / 0 | |
| 0.9.3 | 6 / 0 | |
| 0.9.2 | 6 / 0 | |
| 0.9.0 | 5 / 0 | |
| 0.8.3 | 5 / 0 | |
| 0.8.2 | 5 / 0 | |
| 0.8.1 | 5 / 0 | |
| 0.8.0 | 5 / 0 |
v0.10.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (danielkhalebbatista) than the most recent previously approved version (lukaspiccinibt) on 2024-11-12, but danielkhalebbatista 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.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (lukaspiccinibt) than the most recent previously approved version (danielkhalebbatista) on 2024-09-05, but lukaspiccinibt 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.9.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (lukaspiccinibt) than the most recent previously approved version (danielkhalebbatista) on 2024-09-05, but lukaspiccinibt 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.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (danielkhalebbatista) than the most recent previously approved version (lukaspiccinibt) on 2024-09-02, but danielkhalebbatista 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.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.