@api-client/amf-core
The API Client ecosystem's AMF Core library
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 |
|---|---|---|---|---|
| semgrep | semgrep:shady-links-tlds | AI (semgrep): http://a.ml/ is the AML vocabulary namespace URI, not a C2/exfiltration endpoint; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:amf-client-js | AI (phantom-deps): amf-client-js is a core runtime dep used via config/build tooling; phantom-dep heuristic is a false positive here. | ai | |
| provenance | no-provenance | AI (provenance): Published via GitHub Actions CI; provenance absence is common and not a security signal for this package. | ai | |
| phantom-deps | phantom-dep:@faker-js/faker | AI (phantom-deps): @faker-js/faker is explicitly listed in package.json dependencies; phantom-dep is a false positive here. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.1.14 | 3 / 24 | |
| 0.1.11 | 3 / 24 | |
| 0.1.8 | 3 / 24 | |
| 0.1.5 | 5 / 23 | |
| 0.1.4 | 5 / 23 | |
| 0.1.3 | 5 / 23 |
v0.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.