@wordpress/dataviews
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@wordpress/dom | AI (phantom-deps): Same-org WordPress package, monorepo re-export pattern. | ai | |
| phantom-deps | phantom-dep:@wordpress/url | AI (phantom-deps): Same-org WordPress package, monorepo re-export pattern. | ai | |
| phantom-deps | phantom-dep:@wordpress/theme | AI (phantom-deps): Same-org WordPress package, monorepo re-export pattern. | ai | |
| dependencies | unvetted-dep:@wordpress/icons | AI (dependencies): Official WordPress monorepo sibling package; stable false positive for this org. | ai | |
| dependencies | unvetted-dep:@wordpress/compose | AI (dependencies): Official WordPress monorepo sibling package; stable false positive for this org. | ai | |
| dependencies | unvetted-dep:@wordpress/element | AI (dependencies): Official WordPress monorepo sibling package; stable false positive for this org. | ai | |
| dependencies | unvetted-dep:@wordpress/components | AI (dependencies): Official WordPress monorepo sibling package; stable false positive for this org. | ai | |
| dependencies | unvetted-dep:@wordpress/ui | AI (dependencies): Official WordPress monorepo sibling package; stable false positive for this org. | ai | |
| dependencies | unvetted-dep:@wordpress/private-apis | AI (dependencies): Official WordPress monorepo sibling package; stable false positive for this org. | ai | |
| phantom-deps | phantom-dep:@wordpress/primitives | AI (phantom-deps): Same-org monorepo dep; may be used transitively or in build artifacts. | ai | |
| phantom-deps | phantom-dep:@wordpress/base-styles | AI (phantom-deps): CSS-only package used in build-style output; not directly imported in JS. | ai | |
| dependencies | unvetted-dep:@wordpress/primitives | AI (dependencies): Official WordPress monorepo sibling package; stable false positive for this org. | ai | |
| dependencies | unvetted-dep:@wordpress/data | AI (dependencies): Official WordPress monorepo sibling package; stable false positive for this org. | ai | |
| dependencies | unvetted-dep:@wordpress/date | AI (dependencies): Official WordPress monorepo sibling package; stable false positive for this org. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 17.2.0 | 23 / 10 | |
| 17.1.0 | 21 / 9 | |
| 17.0.1 | 21 / 9 | |
| 17.0.0 | 21 / 9 | |
| 16.0.1 | 22 / 9 | |
| 16.0.0 | 21 / 6 | |
| 15.0.0 | 21 / 6 | |
| 14.3.0 | 21 / 6 | |
| 14.2.0 | 21 / 6 | |
| 14.1.0 | 21 / 6 | |
| 14.0.0 | 21 / 6 | |
| 13.1.0 | 21 / 6 | |
| 13.0.0 | 21 / 6 | |
| 12.0.1 | 24 / 6 | |
| 12.0.0 | 24 / 6 | |
| 11.3.0 | 24 / 6 | |
| 11.2.0 | 24 / 5 | |
| 11.1.0 | 22 / 0 | |
| 11.0.0 | 21 / 0 | |
| 10.3.0 | 20 / 0 | |
| 10.1.7 | 20 / 0 | |
| 10.1.6 | 20 / 0 | |
| 10.1.5 | 20 / 0 | |
| 10.1.4 | 20 / 0 | |
| 10.1.3 | 20 / 0 | |
| 10.1.2 | 20 / 0 |
v17.2.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.
v17.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.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 (gutenbergplugin) than the most recent previously approved version (peterwilsoncc) on 2026-03-04, but gutenbergplugin 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.
v12.0.1
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.
v12.0.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 (gutenbergplugin) than the most recent previously approved version (peterwilsoncc) on 2026-02-18, but gutenbergplugin 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.
v11.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.7
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 (peterwilsoncc) than the most recent previously approved version (gutenbergplugin) on 2026-01-29, but peterwilsoncc 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.
v10.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.