@longtable/core
Provider-neutral domain models and contracts for LongTable
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 0.1.59 | 0 / 1 | |
| 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.59
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.56
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.55
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
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 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
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 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.52
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.51
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
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 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.49
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.48
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.47
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.45
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.44
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.43
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.42
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.41
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.40
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.39
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.37
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.36
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.35
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.34
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.33
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.32
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.31
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.30
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.29
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.28
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.27
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.25
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
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 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.23
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
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 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.21
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.20
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.19
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.18
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.17
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.16
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.15
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
2 findingsPackage name '@longtable/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.