@giphy/js-fetch-api
Javascript API to fetch gifs and stickers from the GIPHY API.
Supply chain provenance
Status for the latest visible version.
Maintainers
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 |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 5.8.0 | 2 / 5 | |
| 5.7.0 | 2 / 5 | |
| 5.6.0 | 2 / 5 | |
| 5.5.0 | 2 / 5 | |
| 5.4.0 | 2 / 5 | |
| 5.3.0 | 3 / 6 | |
| 5.2.0 | 3 / 6 | |
| 5.1.0 | 3 / 6 | |
| 5.0.0 | 3 / 6 |
v5.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.