← Home

@eik/sink

npm Repository Homepage
3
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

trygve-liedigitalsadhutrygve-botleftiefrielewllm

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation; legitimate CI/CD migration for eik-lib org. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers are part of the eik-lib org; consistent with org-level team transition. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of stipsan aligns with org maintainer rotation; no malicious indicators present. ai
provenance slsa-provenance AI (provenance): Package consistently published via CI/CD with Sigstore attestation; SLSA provenance is a stable signal for this package. ai
typosquat typosquat.levenshtein:pino AI (typosquat): Scoped @eik package; name similarity to pino is coincidental, not a typosquat. ai

Versions (showing 3 of 3)

Version Deps Published
1.2.7 0 / 10
1.2.6 0 / 12
1.2.5 0 / 14

v1.2.7

2 findings
HIGH Publisher changed: trygve-bot → GitHub Actions (on 2026-05-28) provenance

This version was published by a different npm account than previous versions on 2026-05-28. 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.2.6

2 findings
HIGH Publisher changed: trygve-bot → GitHub Actions (on 2026-05-27) provenance

This version was published by a different npm account than previous versions on 2026-05-27. 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.2.5

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.