@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, 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 |
|---|---|---|---|---|
| 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 65 of 165)
| Version | Deps | Published |
|---|---|---|
| 0.14.7 | 7 / 5 | |
| 0.14.6 | 7 / 5 | |
| 0.14.5 | 7 / 5 | |
| 0.14.4 | 7 / 5 | |
| 0.14.3 | 7 / 5 | |
| 0.14.2 | 7 / 5 | |
| 0.14.1 | 7 / 5 | |
| 0.14.0 | 7 / 5 | |
| 0.13.0 | 7 / 5 | |
| 0.12.10 | 7 / 5 | |
| 0.12.9 | 7 / 5 | |
| 0.12.8 | 7 / 5 | |
| 0.12.7 | 7 / 5 | |
| 0.12.6 | 7 / 5 | |
| 0.12.5 | 7 / 5 | |
| 0.12.4 | 6 / 5 | |
| 0.12.3 | 6 / 5 | |
| 0.12.2 | 6 / 5 | |
| 0.12.1 | 6 / 5 | |
| 0.12.0 | 6 / 5 | |
| 0.11.1 | 6 / 5 | |
| 0.11.0 | 6 / 5 | |
| 0.10.0 | 6 / 5 | |
| 0.9.2 | 6 / 5 | |
| 0.9.1 | 6 / 5 | |
| 0.9.0 | 6 / 5 | |
| 0.8.4 | 6 / 5 | |
| 0.8.3 | 6 / 5 | |
| 0.8.2 | 6 / 5 | |
| 0.8.1 | 6 / 5 | |
| 0.8.0 | 6 / 6 | |
| 0.7.0 | 6 / 6 | |
| 0.6.3 | 6 / 6 | |
| 0.6.2 | 6 / 6 | |
| 0.6.1 | 6 / 6 | |
| 0.6.0 | 6 / 6 | |
| 0.5.0 | 5 / 6 | |
| 0.4.4 | 5 / 6 | |
| 0.4.3 | 5 / 6 | |
| 0.4.2 | 5 / 6 | |
| 0.4.1 | 5 / 6 | |
| 0.4.0 | 5 / 6 | |
| 0.3.8 | 5 / 6 | |
| 0.3.7 | 5 / 6 | |
| 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.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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.1
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.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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
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.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
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.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.