@cognigy/rest-api-client
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers have Cognigy-namespaced usernames; consistent with internal team management. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Package is actively maintained by Cognigy GmbH; dormancy likely reflects release cadence, not takeover. | ai | |
| phantom-deps | phantom-dep:ajv | AI (phantom-deps): ajv is explicitly declared in dependencies; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:uuidv4 | AI (phantom-deps): uuidv4 is explicitly declared in dependencies; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2026.11.0 | 6 / 35 | |
| 2026.10.0 | 6 / 35 | |
| 2026.9.0 | 6 / 35 | |
| 2026.8.0 | 6 / 35 | |
| 2026.7.0 | 6 / 35 | |
| 2026.5.0 | 6 / 35 | |
| 2025.25.0 | 5 / 34 | |
| 2025.24.0 | 5 / 34 | |
| 2025.23.0 | 5 / 34 |
v2026.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2026.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2025.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2025.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2025.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.