← Home

@eik/sink

npm Repository Homepage
11
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 11 of 11)

Version Deps Published
1.2.7 0 / 10
1.2.6 0 / 12
1.2.5 0 / 14
1.2.4 0 / 13
1.2.3 0 / 12
1.2.2 0 / 12
1.2.1 0 / 11
1.2.0 0 / 11
1.1.0 0 / 14
1.0.2 0 / 14
1.0.0 0 / 7

v1.2.4

1 finding
LOW No provenance attestation provenance

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

v1.2.3

1 finding
LOW No provenance attestation provenance

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

v1.2.2

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

1 finding
LOW No provenance attestation provenance

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

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.2

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.