@apimatic/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
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 @apimatic/core from APIMatic Ltd.; not a typosquat of cors — different namespace and purpose. | ai | |
| phantom-deps | phantom-dep:form-data | AI (phantom-deps): form-data is a declared runtime dep used via config/conditional imports; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:detect-node | AI (phantom-deps): detect-node is a declared runtime dep; phantom-dep heuristic misfires on conditional/indirect usage patterns. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.10.29 | 14 / 21 | |
| 0.10.28 | 14 / 21 | |
| 0.10.27 | 14 / 21 | |
| 0.10.26 | 14 / 17 | |
| 0.10.25 | 14 / 17 | |
| 0.10.24 | 14 / 17 | |
| 0.10.23 | 14 / 17 | |
| 0.10.22 | 14 / 17 | |
| 0.10.21 | 14 / 17 | |
| 0.10.20 | 15 / 17 | |
| 0.10.19 | 15 / 17 |
v0.10.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.