@abaplint/core
Supply chain provenance
Status for the latest visible version.
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
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): @abaplint/core is a scoped ABAP linting package, not a typosquat of cors; Levenshtein match is coincidental. | ai |
Versions (showing 51 of 219)
| Version | Deps | Published |
|---|---|---|
| 2.119.24 | 3 / 11 | |
| 2.119.23 | 3 / 11 | |
| 2.119.22 | 3 / 11 | |
| 2.119.21 | 3 / 11 | |
| 2.119.19 | 3 / 11 | |
| 2.119.18 | 3 / 11 | |
| 2.119.17 | 3 / 11 | |
| 2.119.16 | 3 / 11 | |
| 2.119.15 | 3 / 11 | |
| 2.119.14 | 3 / 11 | |
| 2.119.13 | 3 / 11 | |
| 2.119.12 | 3 / 11 | |
| 2.119.11 | 3 / 11 | |
| 2.119.10 | 3 / 11 | |
| 2.119.9 | 3 / 11 | |
| 2.119.8 | 3 / 11 | |
| 2.119.7 | 3 / 11 | |
| 2.119.6 | 3 / 11 | |
| 2.119.5 | 3 / 11 | |
| 2.119.4 | 3 / 11 | |
| 2.119.3 | 3 / 11 | |
| 2.119.2 | 3 / 11 | |
| 2.119.1 | 3 / 11 | |
| 2.119.0 | 3 / 11 | |
| 2.118.12 | 3 / 11 | |
| 2.118.11 | 3 / 11 | |
| 2.118.10 | 3 / 11 | |
| 2.118.9 | 3 / 11 | |
| 2.118.8 | 3 / 11 | |
| 2.118.7 | 3 / 11 | |
| 2.118.6 | 3 / 11 | |
| 2.118.5 | 3 / 11 | |
| 2.118.4 | 3 / 11 | |
| 2.118.3 | 3 / 11 | |
| 2.118.2 | 3 / 11 | |
| 2.118.1 | 3 / 11 | |
| 2.118.0 | 3 / 11 | |
| 2.117.3 | 3 / 11 | |
| 2.117.2 | 3 / 11 | |
| 2.117.1 | 3 / 11 | |
| 2.117.0 | 3 / 11 | |
| 2.116.1 | 3 / 11 | |
| 2.116.0 | 3 / 11 | |
| 2.115.28 | 3 / 11 | |
| 2.115.27 | 3 / 11 | |
| 2.115.26 | 3 / 11 | |
| 2.115.25 | 3 / 11 | |
| 2.115.24 | 3 / 11 | |
| 2.115.23 | 3 / 11 | |
| 2.115.22 | 3 / 11 | |
| 2.115.21 | 3 / 11 |
v2.119.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.119.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.119.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.119.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.119.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.119.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.119.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.119.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.119.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.119.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.119.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.119.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.119.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.119.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.119.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.119.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.119.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.119.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.119.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.119.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.119.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.119.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.118.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.118.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.118.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.118.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.118.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.118.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.118.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.118.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.118.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.118.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.118.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.118.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.117.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.117.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.117.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.117.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.116.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.116.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.115.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.115.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.115.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.115.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.115.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.115.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.115.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.115.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.