@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, so a manually published version cannot be tied back to a reviewed commit.
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 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 2026.14.0 | 6 / 35 | |
| 2026.13.0 | 6 / 35 | |
| 2026.12.0 | 6 / 35 | |
| 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.6.0 | 6 / 35 | |
| 2026.5.0 | 6 / 35 | |
| 2026.4.0 | 6 / 35 | |
| 2026.3.2 | 6 / 35 | |
| 2026.3.1 | 6 / 35 | |
| 2026.3.0 | 5 / 34 | |
| 2026.1.0 | 5 / 34 | |
| 2025.25.0 | 5 / 34 | |
| 2025.24.0 | 5 / 34 | |
| 2025.23.0 | 5 / 34 |
v2026.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.4.0
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 (lkolapp) than the most recent previously approved version (mayrbenjamin92) on 2026-02-17, but lkolapp 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.
v2026.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.3.1
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 (mayrbenjamin92) than the most recent previously approved version (lkolapp) on 2026-02-05, but mayrbenjamin92 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.
v2026.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2026.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.