← Home

@rivetkit/engine-runner

npm
46
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

nathanflurryanticipate-brave-cookies

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Publisher has 20 approved packages without provenance; consistent pattern, not a new risk. ai
bogus-package bogus-package AI (bogus-package): Internal scoped monorepo package; missing metadata is expected, not a spam/malware indicator. ai
npm-metadata no-description AI (npm-metadata): Consistent pattern across @rivetkit scoped packages; not indicative of malice. ai

Versions (showing 46 of 46)

Version Deps Published
2.3.10 5 / 7
2.3.9 5 / 7
2.3.8 5 / 7
2.3.7 5 / 7
2.3.6 5 / 7
2.3.5 5 / 7
2.3.4 5 / 7
2.3.3 5 / 7
2.3.2 5 / 7
2.3.1 5 / 7
2.3.0 5 / 7
2.2.1 5 / 7
2.2.0 5 / 7
2.1.10 5 / 7
2.1.9 5 / 7
2.1.8 5 / 7
2.1.7 5 / 7
2.1.6 5 / 7
2.1.5 5 / 7
2.1.4 5 / 7
2.1.3 5 / 7
2.1.2 5 / 7
2.1.1 5 / 7
2.1.0 5 / 7
2.0.42 5 / 7
2.0.41 5 / 7
2.0.40 5 / 7
2.0.39 5 / 7
2.0.38 5 / 7
2.0.37 5 / 7
2.0.36 5 / 7
2.0.35 5 / 7
2.0.34 5 / 7
2.0.33 4 / 7
2.0.32 4 / 7
2.0.31 4 / 7
2.0.30 4 / 7
2.0.29 4 / 7
2.0.28 4 / 7
2.0.27 4 / 7
2.0.26 4 / 7
2.0.25 4 / 7
2.0.24 4 / 7
2.0.23 4 / 7
2.0.22 4 / 7
2.0.21 4 / 7

v2.3.10

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.9

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.