@divi/serialized-post
Type declarations for @divi/serialized-post
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:@types/seamless-immutable | AI (dependencies): Standard DefinitelyTyped types package; no security risk for a type-declarations-only package. | ai | |
| provenance | no-provenance | AI (provenance): Commercial Elegant Themes package; provenance absence is consistent across their @divi/* namespace. | ai | |
| phantom-deps | phantom-dep:@types/seamless-immutable | AI (phantom-deps): Types-only package; @types/* deps are often loaded by convention, not direct import. | ai |
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.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.