← Home

@chainlink/cre-sdk-javy-plugin

npm Repository Homepage

Chainlink CRE SDK Javy Plugin.

10
Versions
BUSL-1.1
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

npmserviceaccount-cllm4ussecure.andrewsecure.javiernotoriousenigmasecure.ericzsecure.thanhsecure_handerson

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publisher is confirmed by SLSA provenance attestation; legitimate CI/CD migration for this Chainlink package. ai
semgrep semgrep:env-spread AI (semgrep): Build script utility passing env to child processes; expected pattern for a build tool, not a secret leak risk. ai

Versions (showing 10 of 10)

Version Deps Published
1.7.0 0 / 0
1.6.0 0 / 0
1.5.0 0 / 0
1.2.0 0 / 0
1.1.1 0 / 0
1.1.0 0 / 0
1.0.9 0 / 0
1.0.2 0 / 0
1.0.1 0 / 0
1.0.0 0 / 0

v1.7.0

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.0

2 findings
HIGH env-spread: scripts/shared.ts:15 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/smartcontractkit/cre-sdk-typescript/blob/e31c934b5201195996842b2528add3444977e50b/scripts/shared.ts#L15 13 | cwd, 14 | stdio: 'inherit', > 15 | env: env ? { ...process.env, ...env } : process.env, 16 | }) 17 | p.on('error', reject)

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.5.0

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.2.0

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.1.1

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.1.0

2 findings
HIGH Publisher changed: npmserviceaccount-cll → GitHub Actions (on 2026-02-18) provenance

This version was published by a different npm account than previous versions on 2026-02-18. This could indicate a legitimate maintainer transition or an account compromise.

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.9

2 findings
HIGH Publisher changed: npmserviceaccount-cll → GitHub Actions (on 2026-02-06) provenance

This version was published by a different npm account than previous versions on 2026-02-06. This could indicate a legitimate maintainer transition or an account compromise.

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.2

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.1

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.

v1.0.0

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.