@n8n/tournament
Output compatible rewrite of riot tmpl
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): n8n migrated to GitHub Actions CI publishing; SLSA attestation confirms legitimate org-controlled pipeline. | ai | |
| provenance | missing-githead | AI (provenance): GitHub Actions CI publish flow for n8n monorepo does not emit gitHead; SLSA provenance compensates. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Core template evaluation mechanism; new Function() is intentional and stable for this expression-evaluator package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 3 / 9 | |
| 1.1.1 | 3 / 9 | |
| 1.1.0 | 3 / 9 | |
| 1.0.7 | 3 / 18 | |
| 1.0.6 | 4 / 18 |
v1.2.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v1.1.1
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
v1.1.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-05-05. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.