@flowfuse/nr-project-nodes
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 |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Intentional function deserialization in Node-RED node; guarded by type check, eslint-disable comment confirms awareness. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.7.8 | 5 / 9 | |
| 0.7.7 | 5 / 9 | |
| 0.7.6 | 5 / 9 | |
| 0.7.5 | 5 / 9 | |
| 0.7.4 | 5 / 9 | |
| 0.7.3 | 5 / 9 | |
| 0.7.2 | 5 / 9 | |
| 0.7.1 | 5 / 9 | |
| 0.7.0 | 5 / 9 | |
| 0.6.4 | 2 / 3 | |
| 0.6.3 | 2 / 3 |
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.