@divi/field-library
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/css-tree | AI (phantom-deps): @types/* packages are type-only deps; not directly imported in TS declaration packages by design. | ai | |
| phantom-deps | phantom-dep:@types/codemirror | AI (phantom-deps): @types/* packages are type-only deps; not directly imported in TS declaration packages by design. | ai | |
| phantom-deps | phantom-dep:@types/react-dates | AI (phantom-deps): @types/* packages are type-only deps; not directly imported in TS declaration packages by design. | ai | |
| phantom-deps | phantom-dep:@types/seamless-immutable | AI (phantom-deps): @types/* packages are type-only deps; not directly imported in TS declaration packages by design. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.0.7 | 13 / 0 | |
| 1.0.6 | 13 / 0 | |
| 1.0.5 | 13 / 0 | |
| 1.0.4 | 13 / 0 | |
| 1.0.3 | 13 / 0 | |
| 1.0.2 | 13 / 0 | |
| 1.0.1 | 13 / 0 | |
| 1.0.0 | 13 / 0 |
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.