@wordpress/fields
DataViews is a component that provides an API to render datasets using different types of layouts (table, grid, list, etc.).
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): Same large version gap explains size growth for this actively developed monorepo package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Diff base is many versions behind; reflects unimported intermediate releases, not injected code. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All new deps are official @wordpress/* packages or well-known utils; normal monorepo growth. | ai | |
| provenance | publisher-changed | AI (provenance): peterwilsoncc is a known Gutenberg contributor with strong track record; publisher rotation within the WordPress org is expected. | ai | |
| phantom-deps | phantom-dep:@wordpress/block-editor | AI (phantom-deps): Same-org WordPress package; phantom-dep heuristic commonly misfires on monorepo packages with indirect imports. | ai | |
| dependencies | unvetted-dep:@react-spring/web | AI (dependencies): @react-spring/web is a widely-used animation library; stable false positive for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Gutenberg monorepo package; publisher has 373 approved releases and long track record — dormancy reflects release cadence, not takeover. | ai | |
| phantom-deps | phantom-dep:@wordpress/hooks | AI (phantom-deps): Same-org WordPress package; phantom-dep heuristic false positive for monorepo build artifacts. | ai | |
| phantom-deps | phantom-dep:@wordpress/base-styles | AI (phantom-deps): Same-org WordPress package; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@wordpress/primitives | AI (phantom-deps): Same-org WordPress package; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@wordpress/warning | AI (phantom-deps): Same-org WordPress package; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@wordpress/router | AI (phantom-deps): Same-org WordPress package; stable false positive for this monorepo package. | ai |
Versions (showing 81 of 81)
| Version | Deps | Published |
|---|---|---|
| 0.43.0 | 31 / 0 | |
| 0.42.0 | 30 / 0 | |
| 0.41.1 | 30 / 0 | |
| 0.41.0 | 30 / 0 | |
| 0.40.1 | 31 / 0 | |
| 0.40.0 | 30 / 0 | |
| 0.39.0 | 30 / 0 | |
| 0.38.0 | 30 / 0 | |
| 0.37.0 | 30 / 0 | |
| 0.36.0 | 29 / 0 | |
| 0.35.0 | 29 / 0 | |
| 0.34.0 | 29 / 0 | |
| 0.33.0 | 29 / 0 | |
| 0.32.2 | 29 / 0 | |
| 0.32.1 | 29 / 0 | |
| 0.32.0 | 29 / 0 | |
| 0.31.0 | 28 / 0 | |
| 0.30.0 | 28 / 0 | |
| 0.29.0 | 28 / 0 | |
| 0.28.0 | 28 / 0 | |
| 0.27.0 | 28 / 0 | |
| 0.26.0 | 28 / 0 | |
| 0.25.11 | 28 / 0 | |
| 0.25.10 | 28 / 0 | |
| 0.25.9 | 28 / 0 | |
| 0.25.8 | 28 / 0 | |
| 0.25.7 | 28 / 0 | |
| 0.25.6 | 28 / 0 | |
| 0.25.5 | 28 / 0 | |
| 0.25.4 | 28 / 0 | |
| 0.25.3 | 28 / 0 | |
| 0.25.2 | 28 / 0 | |
| 0.25.1 | 28 / 0 | |
| 0.25.0 | 28 / 0 | |
| 0.24.0 | 28 / 0 | |
| 0.23.0 | 28 / 0 | |
| 0.22.0 | 28 / 0 | |
| 0.21.0 | 28 / 0 | |
| 0.20.0 | 28 / 0 | |
| 0.19.0 | 28 / 0 | |
| 0.18.0 | 28 / 0 | |
| 0.17.0 | 28 / 0 | |
| 0.16.0 | 28 / 0 | |
| 0.15.0 | 28 / 0 | |
| 0.14.0 | 28 / 0 | |
| 0.13.0 | 28 / 0 | |
| 0.12.0 | 28 / 0 | |
| 0.11.6 | 28 / 0 | |
| 0.11.5 | 28 / 0 | |
| 0.11.4 | 28 / 0 | |
| 0.11.3 | 28 / 0 | |
| 0.11.2 | 28 / 0 | |
| 0.11.1 | 28 / 0 | |
| 0.11.0 | 28 / 0 | |
| 0.10.0 | 28 / 0 | |
| 0.9.0 | 28 / 0 | |
| 0.8.0 | 28 / 0 | |
| 0.7.1 | 28 / 0 | |
| 0.7.0 | 28 / 0 | |
| 0.6.0 | 28 / 0 | |
| 0.5.0 | 27 / 0 | |
| 0.4.0 | 26 / 0 | |
| 0.3.0 | 25 / 0 | |
| 0.2.0 | 22 / 0 | |
| 0.1.0 | 22 / 0 | |
| 0.0.17 | 21 / 0 | |
| 0.0.16 | 21 / 0 | |
| 0.0.15 | 21 / 0 | |
| 0.0.14 | 21 / 0 | |
| 0.0.13 | 21 / 0 | |
| 0.0.12 | 21 / 0 | |
| 0.0.11 | 21 / 0 | |
| 0.0.10 | 21 / 0 | |
| 0.0.9 | 21 / 0 | |
| 0.0.8 | 21 / 0 | |
| 0.0.7 | 21 / 0 | |
| 0.0.6 | 21 / 0 | |
| 0.0.5 | 21 / 0 | |
| 0.0.4 | 21 / 0 | |
| 0.0.3 | 21 / 0 | |
| 0.0.2 | 21 / 0 |
v0.43.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (desrosj) than the most recent previously approved version (gutenbergplugin) on 2026-07-14, but desrosj is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (desrosj) than the most recent previously approved version (gutenbergplugin) on 2026-06-30, but desrosj is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.14.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gziolo) than the most recent previously approved version (gutenbergplugin) on 2025-04-11, but gziolo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gziolo) than the most recent previously approved version (gutenbergplugin) on 2025-01-03, but gziolo is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.