@templatical/renderer
Render Templatical email templates to MJML
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): New package without provenance setup; common and not a security signal on its own. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 0.19.0 | 1 / 4 | |
| 0.18.0 | 1 / 4 | |
| 0.17.1 | 1 / 4 | |
| 0.17.0 | 1 / 4 | |
| 0.16.5 | 1 / 4 | |
| 0.16.4 | 1 / 4 | |
| 0.16.3 | 1 / 4 | |
| 0.16.2 | 1 / 4 | |
| 0.16.1 | 1 / 4 | |
| 0.16.0 | 1 / 4 | |
| 0.15.1 | 1 / 4 | |
| 0.15.0 | 1 / 4 | |
| 0.14.0 | 1 / 4 | |
| 0.13.0 | 1 / 4 | |
| 0.12.1 | 1 / 4 | |
| 0.12.0 | 1 / 4 | |
| 0.11.1 | 1 / 4 | |
| 0.11.0 | 1 / 4 | |
| 0.10.4 | 1 / 4 | |
| 0.10.3 | 1 / 4 | |
| 0.10.2 | 1 / 4 | |
| 0.10.1 | 1 / 4 | |
| 0.10.0 | 1 / 5 | |
| 0.9.1 | 1 / 5 | |
| 0.9.0 | 1 / 5 | |
| 0.8.5 | 1 / 5 | |
| 0.8.4 | 1 / 5 | |
| 0.8.3 | 1 / 5 | |
| 0.8.2 | 1 / 5 | |
| 0.8.1 | 1 / 5 | |
| 0.8.0 | 1 / 5 | |
| 0.7.3 | 1 / 5 | |
| 0.7.2 | 1 / 5 | |
| 0.7.1 | 1 / 5 | |
| 0.7.0 | 1 / 4 | |
| 0.6.7 | 1 / 4 | |
| 0.6.6 | 1 / 4 | |
| 0.6.5 | 1 / 4 | |
| 0.6.4 | 1 / 4 | |
| 0.6.3 | 1 / 4 | |
| 0.6.2 | 1 / 4 | |
| 0.6.1 | 1 / 4 | |
| 0.5.1 | 1 / 4 | |
| 0.5.0 | 1 / 4 | |
| 0.0.6 | 1 / 3 | |
| 0.0.5 | 1 / 3 | |
| 0.0.4 | 1 / 3 | |
| 0.0.3 | 1 / 3 | |
| 0.0.2 | 1 / 3 | |
| 0.0.1 | 1 / 3 |
v0.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.