@principal-ai/principal-view-cli
Principal View CLI - Validate and manage .canvas configuration files
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are same-org @principal-ai/* scoped packages; consistent with internal library growth. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size growth driven by adding two first-party @principal-ai/* deps; consistent with organic feature expansion in a CLI tool. | ai | |
| source-diff | large-new-source-files | AI (source-diff): 56 new files align with bundling two new first-party scoped packages into the CLI distribution. | ai | |
| phantom-deps | phantom-dep:glob | AI (phantom-deps): glob is explicitly declared as a runtime dependency; phantom-dep is a false positive for this CLI package. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 0.24.0 | 9 / 5 | |
| 0.23.0 | 9 / 5 | |
| 0.22.1 | 9 / 5 | |
| 0.22.0 | 9 / 5 | |
| 0.21.0 | 9 / 5 | |
| 0.20.0 | 9 / 5 | |
| 0.18.6 | 8 / 5 | |
| 0.18.5 | 8 / 5 | |
| 0.18.4 | 8 / 5 | |
| 0.18.3 | 8 / 5 | |
| 0.18.1 | 8 / 5 | |
| 0.18.0 | 8 / 5 | |
| 0.3.6 | 6 / 5 | |
| 0.3.2 | 5 / 6 | |
| 0.1.31 | 5 / 6 | |
| 0.1.30 | 4 / 6 | |
| 0.1.29 | 4 / 6 | |
| 0.1.28 | 4 / 6 | |
| 0.1.27 | 4 / 6 | |
| 0.1.26 | 4 / 6 | |
| 0.1.25 | 4 / 6 | |
| 0.1.24 | 4 / 6 | |
| 0.1.23 | 4 / 6 | |
| 0.1.22 | 4 / 6 | |
| 0.1.21 | 4 / 6 | |
| 0.1.20 | 4 / 6 | |
| 0.1.19 | 4 / 6 | |
| 0.1.18 | 4 / 6 | |
| 0.1.17 | 4 / 6 | |
| 0.1.16 | 4 / 6 | |
| 0.1.15 | 4 / 6 | |
| 0.1.14 | 4 / 6 | |
| 0.1.13 | 4 / 6 |
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.