@getzep/zep-js
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
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): zep-org maintainers on official scoped package; legitimate handoff. | ai | |
| provenance | missing-githead | AI (provenance): Publish-env change for a legit SDK rewrite; no malicious behavior. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod used in generated schema/config; stable FP for this SDK. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.0.2 | 5 / 12 | |
| 2.0.1 | 5 / 14 | |
| 2.0.0 | 5 / 14 | |
| 0.9.0 | 3 / 20 |
v2.0.1
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: paulzep.
This version was published by a different npm account (paulzep) than the most recent previously approved version (danielchalef) on 2024-09-26. It has since remained available on npm for 660 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.
v2.0.0
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: paulzep.
This version was published by a different npm account (paulzep) than the most recent previously approved version (danielchalef) on 2024-09-25. It has since remained available on npm for 661 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.