@giphy/js-fetch-api
Javascript API to fetch gifs and stickers from the GIPHY API.
3
Versions
MIT
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
gitHead linked
Maintainers
giphy
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from manual (giphy account) to GitHub Actions CI/CD with SLSA provenance; legitimate for this org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long-lived official Giphy package resuming publishes via CI/CD; dormancy is normal for stable libs. | ai | |
| dependencies | unvetted-dep:@giphy/js-util | AI (dependencies): @giphy/js-util is a first-party sibling package in the same Giphy monorepo, published by the same trusted giphy publisher. Wildcard constraint is a standard monorepo pattern. | ai | |
| dependencies | unvetted-dep:@giphy/js-types | AI (dependencies): @giphy/js-types is a first-party sibling package in the same Giphy monorepo, published by the same trusted giphy publisher. Wildcard constraint is a standard monorepo pattern. | ai | |
| provenance | no-provenance | AI (provenance): Absence of Sigstore provenance is common across npm; publisher is the verified official Giphy org with a long track record. Not a meaningful risk signal for this package. | ai |
v5.8.0
2 findings
HIGH
Publisher changed: giphy → GitHub Actions (on 2026-05-01)
provenance
This version was published by a different npm account than previous versions on 2026-05-01. This could indicate a legitimate maintainer transition or an account compromise.
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.6.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.