@eik/sink-memory
In-memory sink designed for tests.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Package has SLSA provenance attestation via CI/CD; maintainer addition in the eik-lib org is a normal team operation and does not indicate compromise. | ai | |
| dependencies | unvetted-dep:@eik/sink | AI (dependencies): First-party @eik ecosystem dependency; same org as this package. No risk signal beyond being unvetted in the registry. | ai | |
| dependencies | unvetted-dep:@eik/common | AI (dependencies): First-party @eik ecosystem dependency; same org as this package. No risk signal beyond being unvetted in the registry. | ai | |
| dependencies | unvetted-dep:@metrics/client | AI (dependencies): Metrics client dependency used consistently across the @eik ecosystem. No risk signal beyond being unvetted in the registry. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 2.0.34 | 3 / 9 | |
| 2.0.33 | 3 / 9 | |
| 2.0.32 | 3 / 9 | |
| 2.0.31 | 3 / 9 | |
| 2.0.30 | 3 / 11 | |
| 2.0.29 | 3 / 11 | |
| 2.0.28 | 3 / 11 | |
| 2.0.27 | 3 / 11 | |
| 2.0.26 | 3 / 11 | |
| 2.0.25 | 3 / 11 | |
| 2.0.24 | 3 / 11 | |
| 2.0.23 | 3 / 11 | |
| 2.0.22 | 3 / 11 | |
| 2.0.21 | 3 / 11 | |
| 2.0.20 | 3 / 11 | |
| 2.0.19 | 3 / 11 | |
| 2.0.18 | 3 / 11 | |
| 2.0.17 | 3 / 11 | |
| 2.0.16 | 3 / 11 | |
| 2.0.15 | 3 / 11 | |
| 2.0.14 | 3 / 11 | |
| 2.0.13 | 3 / 11 | |
| 2.0.12 | 3 / 11 | |
| 2.0.11 | 3 / 11 | |
| 2.0.10 | 3 / 11 | |
| 2.0.9 | 3 / 11 | |
| 2.0.8 | 3 / 11 | |
| 2.0.7 | 3 / 11 | |
| 2.0.6 | 3 / 11 | |
| 2.0.5 | 3 / 11 |
v2.0.34
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.33
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.32
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.31
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.30
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.