@divi/rest
Type declarations for @divi/rest
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@divi/window | AI (dependencies): Sibling @divi/* package from same Elegant Themes publisher; type-only ecosystem, no execution risk. | ai | |
| dependencies | unvetted-dep:@divi/types-external | AI (dependencies): Sibling @divi/* package from same Elegant Themes publisher; type-only ecosystem, no execution risk. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): @divi/rest is a scoped package by Elegant Themes; no relation to jest. | ai | |
| typosquat | typosquat.levenshtein:next | AI (typosquat): @divi/rest is a scoped package by Elegant Themes; no relation to next. | ai | |
| typosquat | typosquat.levenshtein:react | AI (typosquat): @divi/rest is a scoped package by Elegant Themes; no relation to react. | ai | |
| phantom-deps | phantom-dep:@types/seamless-immutable | AI (phantom-deps): Type-only package; @types deps are commonly declared but not directly imported. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.0.4 | 4 / 0 | |
| 1.0.3 | 4 / 0 | |
| 1.0.2 | 4 / 0 | |
| 1.0.1 | 4 / 0 | |
| 1.0.0 | 4 / 0 |
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
2 findingsPackage name '@divi/rest' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
2 findingsPackage name '@divi/rest' is 1 edit(s) away from popular package 'jest'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.