@tmagic/core Apache-2.0 24 versions

@tmagic/core

npm Repository Homepage

24

Versions

Apache-2.0

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

jia000

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:cors	AI (typosquat): Tencent's tmagic-editor monorepo package; scoped @tmagic namespace, not a typosquat of cors.	ai	2026/05/01
semgrep	semgrep:eval-usage	AI (semgrep): eval() in DevtoolApi.ts validates user-supplied function strings in a devtools context; not a supply-chain risk.	ai	2026/05/01
dependencies	unvetted-dep:@tmagic/dep	AI (dependencies): Sibling monorepo package from same Tencent tmagic-editor project.	ai	2026/05/01
dependencies	unvetted-dep:@tmagic/utils	AI (dependencies): Sibling monorepo package from same Tencent tmagic-editor project.	ai	2026/05/01
dependencies	unvetted-dep:@tmagic/schema	AI (dependencies): Sibling monorepo package from same Tencent tmagic-editor project.	ai	2026/05/01
dependencies	unvetted-dep:@tmagic/data-source	AI (dependencies): Sibling monorepo package from same Tencent tmagic-editor project.	ai	2026/05/01

Versions (showing 24 of 24)

Version	Deps	Published
1.7.13	6 / 2	2026-04-29
1.7.12	6 / 2	2026-04-24
1.7.11	6 / 2	2026-04-23
1.7.10	6 / 2	2026-04-13
1.7.9	6 / 2	2026-03-23
1.7.8	6 / 2	2026-03-20
1.7.7	6 / 2	2026-03-12
1.7.6	6 / 2	2026-01-19
1.7.5	6 / 2	2026-01-08
1.7.4	6 / 2	2025-12-29
1.7.3	6 / 2	2025-12-25
1.7.2	6 / 2	2025-12-09
1.7.1	6 / 2	2025-12-09
1.7.0	6 / 2	2025-12-04
1.6.1	6 / 2	2025-10-14
1.6.0	6 / 2	2025-08-27
1.5.24	6 / 2	2025-07-03
1.5.23	6 / 2	2025-07-03
1.5.22	6 / 2	2025-06-09
1.5.21	6 / 2	2025-06-04
1.5.20	6 / 2	2025-05-21
1.5.19	6 / 2	2025-05-20
1.5.18	6 / 2	2025-05-14
1.5.17	6 / 2	2025-05-06

v1.7.13

2 findings

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

Package name '@tmagic/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.

v1.7.12

1 finding

LOW No provenance attestation provenance

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

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

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

v1.7.9

1 finding

LOW No provenance attestation provenance

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

v1.7.8

1 finding

LOW No provenance attestation provenance

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

v1.7.7

1 finding

LOW No provenance attestation provenance

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

v1.7.6

1 finding

LOW No provenance attestation provenance

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

v1.7.5

1 finding

LOW No provenance attestation provenance

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

v1.7.4

1 finding

LOW No provenance attestation provenance

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

v1.7.3

1 finding

LOW No provenance attestation provenance

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

v1.7.2

1 finding

LOW No provenance attestation provenance

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

v1.7.1

1 finding

LOW No provenance attestation provenance

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

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

v1.6.1

1 finding

LOW No provenance attestation provenance

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

v1.6.0

1 finding

LOW No provenance attestation provenance

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

v1.5.24

1 finding

LOW No provenance attestation provenance

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

v1.5.23

1 finding

LOW No provenance attestation provenance

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

v1.5.22

1 finding

LOW No provenance attestation provenance

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

v1.5.21

1 finding

LOW No provenance attestation provenance

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

v1.5.20

1 finding

LOW No provenance attestation provenance

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

v1.5.19

1 finding

LOW No provenance attestation provenance

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

v1.5.18

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

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.