← Home

@bolttech/templating-sdk

JavaScript SDK for Bolttech Templating Service - Create, manage and render templates with ease

5
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

andsfranboltdanielkhalebbatistapauloazevedo-edbruno.gomesplinio.altoejoaoteixeira20esteve-cabrerajabolttechlucasvpaivaherberts.fortunamatheus.maciel.bolttechsilas.silva.bolttech

Keywords

templatingtemplatebolttechsdkjavascripttypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Bolttech internal SDK; lack of provenance is common and not a risk indicator here. ai
dependencies unvetted-dep:handlebars AI (dependencies): handlebars is a well-established library; ^4.7.8 is a safe, patched version range. ai
phantom-deps phantom-dep:qrcode-svg AI (phantom-deps): qrcode-svg is a declared runtime dep; phantom-dep heuristic fires because it may be used indirectly via SDK internals rather than direct import. ai

Versions (showing 5 of 5)

Version Deps Published
0.2.12 3 / 21
0.2.11 3 / 22
0.2.10 3 / 22
0.2.1 2 / 22
0.1.1 2 / 22

v0.2.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.