← Home

@tachybase/plugin-adapter-red-node

npm Repository Homepage

Integrate and manage RedNode workflow automation engine.

6
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

sealdaytomyjan

Keywords

System management

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Internal monorepo plugin; missing repo/homepage is consistent across @tachybase packages, not a spam indicator. ai
npm-metadata bundled-binaries AI (npm-metadata): Binary is bcrypt native binding from @node-red/editor-api, a legitimate Node-RED dependency; SLSA provenance confirms CI/CD build integrity. ai

Versions (showing 6 of 6)

Version Deps Published
1.6.21 0 / 12
1.6.20 0 / 12
1.6.19 0 / 12
1.6.18 0 / 12
1.6.17 0 / 12
1.0.25 5 / 3

v1.6.21

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.6.20

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.6.19

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.6.18

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.0.25

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.