@principal-ai/principal-view-react
React components for graph-based principal view framework
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:themed-markdown | AI (dependencies): themed-markdown appears to be an org-adjacent package used for markdown theming; consistent with this package's purpose. | ai | |
| phantom-deps | phantom-dep:@principal-ai/codebase-composition | AI (phantom-deps): Same-org dependency; phantom-dep pattern is stable for this package's config-level usage. | ai | |
| phantom-deps | phantom-dep:elkjs | AI (phantom-deps): elkjs is a graph layout library consistent with this package's purpose; config-level reference is expected. | ai | |
| phantom-deps | phantom-dep:remark-gfm | AI (phantom-deps): Declared runtime dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:rehype-slug | AI (phantom-deps): Declared runtime dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:highlight.js | AI (phantom-deps): Declared runtime dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:react-markdown | AI (phantom-deps): Declared runtime dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:js-yaml | AI (phantom-deps): Declared runtime dep; likely used transitively or re-exported through themed-markdown bundle. | ai | |
| phantom-deps | phantom-dep:rehype-highlight | AI (phantom-deps): Declared runtime dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:hast-util-sanitize | AI (phantom-deps): Declared runtime dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:react-zoom-pan-pinch | AI (phantom-deps): Declared runtime dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:rehype-sanitize | AI (phantom-deps): Declared runtime dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:zustand | AI (phantom-deps): Declared runtime dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:rehype-raw | AI (phantom-deps): Declared runtime dep; stable false positive for this package. | ai |
Versions (showing 51 of 162)
| Version | Deps | Published |
|---|---|---|
| 0.15.9 | 15 / 16 | |
| 0.15.8 | 15 / 16 | |
| 0.15.7 | 15 / 16 | |
| 0.15.6 | 15 / 16 | |
| 0.15.5 | 15 / 16 | |
| 0.15.4 | 15 / 16 | |
| 0.15.3 | 15 / 16 | |
| 0.15.2 | 15 / 16 | |
| 0.15.1 | 15 / 16 | |
| 0.15.0 | 15 / 16 | |
| 0.14.38 | 15 / 16 | |
| 0.14.37 | 15 / 16 | |
| 0.14.36 | 15 / 16 | |
| 0.14.35 | 15 / 16 | |
| 0.14.34 | 15 / 16 | |
| 0.14.33 | 15 / 16 | |
| 0.14.32 | 15 / 16 | |
| 0.14.31 | 15 / 16 | |
| 0.14.30 | 15 / 16 | |
| 0.14.29 | 15 / 16 | |
| 0.14.28 | 15 / 16 | |
| 0.14.27 | 15 / 16 | |
| 0.14.26 | 15 / 16 | |
| 0.14.25 | 15 / 16 | |
| 0.14.24 | 15 / 16 | |
| 0.14.23 | 15 / 16 | |
| 0.14.22 | 15 / 16 | |
| 0.14.21 | 15 / 16 | |
| 0.14.19 | 15 / 16 | |
| 0.14.18 | 15 / 16 | |
| 0.14.17 | 15 / 16 | |
| 0.14.16 | 15 / 16 | |
| 0.14.15 | 15 / 16 | |
| 0.14.14 | 15 / 16 | |
| 0.14.13 | 15 / 16 | |
| 0.14.12 | 15 / 16 | |
| 0.14.11 | 15 / 16 | |
| 0.14.10 | 15 / 16 | |
| 0.14.9 | 15 / 16 | |
| 0.14.8 | 15 / 16 | |
| 0.14.7 | 15 / 16 | |
| 0.14.6 | 15 / 16 | |
| 0.14.5 | 14 / 16 | |
| 0.14.4 | 14 / 16 | |
| 0.14.3 | 14 / 16 | |
| 0.14.2 | 14 / 16 | |
| 0.14.1 | 14 / 16 | |
| 0.14.0 | 14 / 16 | |
| 0.13.30 | 14 / 16 | |
| 0.13.29 | 14 / 16 | |
| 0.13.28 | 14 / 16 |
v0.15.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.