← Home

@funkit/core

npm Repository Homepage
90
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

chloe-tanaaronikerfun-dkimdostaherringtondarkholme

Keywords

Fun WalletEthereumAccount AbstractionSDK

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:dotenv AI (phantom-deps): Config/test tooling dependency; not a runtime import concern for this SDK. ai
phantom-deps phantom-dep:ethers AI (phantom-deps): ethers is a core Web3 dependency; likely re-exported or used indirectly in the bundle. ai
phantom-deps phantom-dep:@ethersproject/providers AI (phantom-deps): Ethersproject sub-package; consistent with ethers v5 monorepo usage pattern. ai
phantom-deps phantom-dep:@aws-sdk/client-secrets-manager AI (phantom-deps): Framework-scoped/test dependency for AWS-based test scripts; stable false positive. ai
typosquat typosquat.levenshtein:cors AI (typosquat): @funkit/core is a legitimate scoped SDK package, not a typosquat of cors; name similarity is coincidental. ai

Versions (showing 90 of 90)

Version Deps Published
2.3.68 7 / 7
2.3.67 7 / 7
2.3.66 7 / 7
2.3.65 7 / 7
2.3.64 7 / 7
2.3.63 7 / 7
2.3.62 7 / 7
2.3.61 7 / 7
2.3.60 7 / 7
2.3.59 7 / 7
2.3.58 7 / 7
2.3.57 7 / 7
2.3.56 10 / 4
2.3.55 10 / 4
2.3.54 10 / 4
2.3.53 10 / 4
2.3.52 10 / 4
2.3.51 10 / 4
2.3.50 10 / 4
2.3.49 10 / 4
2.3.48 10 / 4
2.3.47 10 / 4
2.3.46 10 / 4
2.3.45 10 / 4
2.3.44 10 / 4
2.3.43 10 / 4
2.3.42 10 / 4
2.3.41 10 / 4
2.3.40 10 / 4
2.3.39 10 / 4
2.3.38 10 / 4
2.3.37 10 / 4
2.3.36 11 / 3
2.3.35 11 / 3
2.3.34 11 / 3
2.3.33 11 / 3
2.3.32 11 / 3
2.3.31 11 / 3
2.3.30 11 / 3
2.3.29 11 / 3
2.3.28 11 / 3
2.3.27 11 / 3
2.3.26 11 / 3
2.3.25 11 / 3
2.3.24 11 / 3
2.3.23 11 / 3
2.3.22 11 / 3
2.3.21 11 / 3
2.3.20 11 / 3
2.3.19 11 / 3
2.3.18 11 / 3
2.3.17 11 / 3
2.3.16 11 / 3
2.3.15 11 / 3
2.3.14 11 / 3
2.3.13 11 / 3
2.3.12 11 / 3
2.3.11 11 / 3
2.3.10 11 / 3
2.3.9 11 / 3
2.3.8 11 / 3
2.3.7 11 / 3
2.3.6 11 / 3
2.3.5 11 / 3
2.3.4 11 / 3
2.3.3 12 / 3
2.3.2 12 / 3
2.3.1 11 / 3
2.3.0 13 / 10
2.2.9 16 / 10
2.2.8 15 / 10
2.2.7 15 / 10
2.2.6 15 / 10
2.2.5 15 / 18
2.2.4 15 / 18
2.2.3 15 / 18
2.2.2 15 / 18
2.2.1 15 / 18
2.2.0 15 / 18
2.1.8 15 / 18
2.1.7 15 / 18
2.1.6 15 / 18
2.1.5 15 / 18
2.1.4 15 / 18
2.1.3 15 / 18
2.1.2 15 / 18
2.1.1 16 / 18
2.1.0 16 / 18
2.0.1 16 / 18
2.0.0 16 / 18

v2.3.15

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.

v2.3.14

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.

v2.3.13

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.

v2.3.12

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.

v2.3.11

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.

v2.3.10

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.

v2.3.9

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.

v2.3.8

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.

v2.3.7

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.

v2.3.6

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.

v2.3.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.

v2.3.4

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.

v2.3.3

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.

v2.3.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.

v2.3.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.

v2.3.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.

v2.2.9

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.

v2.2.8

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.

v2.2.7

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.

v2.2.6

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.

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

v2.2.4

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.

v2.2.3

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.

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

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

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

v2.1.8

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.

v2.1.7

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.

v2.1.6

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.

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

v2.1.4

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.

v2.1.3

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.

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

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

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

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

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