@apimatic/core
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Manual→GitHub Actions CI/CD with SLSA attestation; legitimate org transition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Org maintainer handoff alongside provenance improvement; no malicious change. | ai | |
| 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 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 0.10.30 | 14 / 21 | |
| 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 | |
| 0.10.18 | 15 / 17 | |
| 0.10.17 | 15 / 17 | |
| 0.10.16 | 15 / 17 | |
| 0.10.15 | 15 / 17 | |
| 0.10.14 | 15 / 17 | |
| 0.10.13 | 15 / 17 | |
| 0.10.12 | 15 / 17 | |
| 0.10.11 | 15 / 17 | |
| 0.10.10 | 15 / 17 | |
| 0.10.9 | 15 / 17 | |
| 0.10.8 | 15 / 17 | |
| 0.10.7 | 15 / 17 | |
| 0.10.6 | 15 / 17 | |
| 0.10.5 | 14 / 16 | |
| 0.7.3 | 9 / 16 | |
| 0.7.1 | 9 / 16 | |
| 0.6.2 | 8 / 16 | |
| 0.6.1 | 8 / 17 |
v0.10.30
2 findingsThis version was published by a different npm account than previous versions on 2026-07-09. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.8
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (apimaticdev) than the most recent previously approved version (hamzamahmood) on 2024-05-28, but apimaticdev is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
2 findingsThis version was published by a different npm account (maryamadnan3) than the most recent previously approved version (wajahatiqbal) on 2024-03-19. It has since remained available on npm for 856 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
2 findingsThis version was published by a different npm account (wajahatiqbal) than the most recent previously approved version (mehdi991) on 2022-01-03. It has since remained available on npm for 1662 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wajahatiqbal.
This version was published by a different npm account (wajahatiqbal) than the most recent previously approved version (mehdi991) on 2021-09-29. It has since remained available on npm for 1758 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.