@funkit/core No license 53 versions

@funkit/core

npm Repository Homepage

53

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

chloe-tanaaronikerfun-dkimdostaherringtondarkholme

Keywords

Fun WalletEthereumAccount AbstractionSDK

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:dotenv	AI (phantom-deps): Config/test tooling dependency; not a runtime import concern for this SDK.	ai	2026/05/24
phantom-deps	phantom-dep:ethers	AI (phantom-deps): ethers is a core Web3 dependency; likely re-exported or used indirectly in the bundle.	ai	2026/05/24
phantom-deps	phantom-dep:@ethersproject/providers	AI (phantom-deps): Ethersproject sub-package; consistent with ethers v5 monorepo usage pattern.	ai	2026/05/24
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	2026/05/24
typosquat	typosquat.levenshtein:cors	AI (typosquat): @funkit/core is a legitimate scoped SDK package, not a typosquat of cors; name similarity is coincidental.	ai	2026/05/18

Versions (showing 53 of 53)

Version	Deps	Published
2.3.68	7 / 7	2025-12-08
2.3.67	7 / 7	2025-12-08
2.3.66	7 / 7	2025-12-02
2.3.65	7 / 7	2025-11-25
2.3.64	7 / 7	2025-11-23
2.3.63	7 / 7	2025-11-21
2.3.62	7 / 7	2025-11-21
2.3.61	7 / 7	2025-11-19
2.3.60	7 / 7	2025-11-19
2.3.59	7 / 7	2025-11-13
2.3.58	7 / 7	2025-11-13
2.3.57	7 / 7	2025-11-11
2.3.56	10 / 4	2025-11-03
2.3.55	10 / 4	2025-10-30
2.3.54	10 / 4	2025-10-28
2.3.53	10 / 4	2025-10-23
2.3.52	10 / 4	2025-10-21
2.3.51	10 / 4	2025-10-16
2.3.50	10 / 4	2025-10-14
2.3.49	10 / 4	2025-10-09
2.3.48	10 / 4	2025-10-07
2.3.47	10 / 4	2025-09-30
2.3.46	10 / 4	2025-09-25
2.3.45	10 / 4	2025-09-23
2.3.44	10 / 4	2025-09-15
2.3.43	10 / 4	2025-09-11
2.3.42	10 / 4	2025-09-09
2.3.41	10 / 4	2025-09-03
2.3.40	10 / 4	2025-08-29
2.3.39	10 / 4	2025-08-27
2.3.38	10 / 4	2025-08-26
2.3.37	10 / 4	2025-08-22
2.3.36	11 / 3	2025-08-20
2.3.35	11 / 3	2025-08-19
2.3.34	11 / 3	2025-08-12
2.3.33	11 / 3	2025-08-11
2.3.32	11 / 3	2025-08-07
2.3.31	11 / 3	2025-08-05
2.3.30	11 / 3	2025-08-01
2.3.29	11 / 3	2025-07-25
2.3.28	11 / 3	2025-07-24
2.3.27	11 / 3	2025-07-21
2.3.26	11 / 3	2025-07-02
2.3.25	11 / 3	2025-06-30
2.3.24	11 / 3	2025-06-29
2.3.23	11 / 3	2025-06-27
2.3.22	11 / 3	2025-06-25
2.3.21	11 / 3	2025-06-20
2.3.20	11 / 3	2025-06-17
2.3.19	11 / 3	2025-06-06
2.3.18	11 / 3	2025-06-03
2.3.17	11 / 3	2025-05-30
2.3.16	11 / 3	2025-05-21

v2.3.68

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'cors' typosquat

Package name '@funkit/core' is 1 edit(s) away from popular package 'cors'.

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.