← Home

@longtable/core

npm Repository Homepage

Provider-neutral domain models and contracts for LongTable

47
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

newhosung

Keywords

longtableresearchcontractstypes

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:cors AI (typosquat): Scoped package @longtable/core; 'core' suffix in a scoped namespace is not a typosquat of 'cors'. ai

Versions (showing 47 of 47)

Version Deps Published
0.1.56 0 / 1
0.1.55 0 / 1
0.1.54 0 / 1
0.1.53 0 / 1
0.1.52 0 / 1
0.1.51 0 / 1
0.1.50 0 / 1
0.1.49 0 / 1
0.1.48 0 / 1
0.1.47 0 / 1
0.1.45 0 / 1
0.1.44 0 / 1
0.1.43 0 / 1
0.1.42 0 / 1
0.1.41 0 / 1
0.1.40 0 / 1
0.1.39 0 / 1
0.1.38 0 / 1
0.1.37 0 / 1
0.1.36 0 / 1
0.1.35 0 / 1
0.1.34 0 / 1
0.1.33 0 / 1
0.1.32 0 / 1
0.1.31 0 / 1
0.1.30 0 / 1
0.1.29 0 / 1
0.1.28 0 / 1
0.1.27 0 / 1
0.1.26 0 / 1
0.1.25 0 / 1
0.1.24 0 / 1
0.1.23 0 / 1
0.1.22 0 / 1
0.1.21 0 / 1
0.1.20 0 / 1
0.1.19 0 / 1
0.1.18 0 / 1
0.1.17 0 / 1
0.1.16 0 / 1
0.1.15 0 / 1
0.1.14 0 / 1
0.1.13 0 / 1
0.1.12 0 / 1
0.1.11 0 / 1
0.1.10 0 / 1
0.1.9 0 / 1

v0.1.56

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

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

v0.1.55

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

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

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.54

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

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

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.53

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

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

v0.1.52

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

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

v0.1.51

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

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

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.50

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

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

v0.1.49

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

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

v0.1.48

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

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

v0.1.47

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

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

v0.1.45

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

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

v0.1.44

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

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

v0.1.43

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

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

v0.1.42

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

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

v0.1.41

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

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

v0.1.40

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

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

v0.1.39

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

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

v0.1.37

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

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

v0.1.36

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

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

v0.1.35

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

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

v0.1.34

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

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

v0.1.33

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

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

v0.1.32

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

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

v0.1.31

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

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

v0.1.30

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

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

v0.1.29

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

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

v0.1.28

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

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

v0.1.27

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

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

v0.1.25

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

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

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.24

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

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

v0.1.23

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

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

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.22

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

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

v0.1.21

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

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

v0.1.20

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

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

v0.1.19

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

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

v0.1.18

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

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

v0.1.17

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

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

v0.1.16

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

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

v0.1.15

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

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

v0.1.13

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

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

v0.1.12

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

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

v0.1.11

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

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

v0.1.10

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

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