@principal-ai/principal-view-core
Core logic and types 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:handlebars | AI (dependencies): Handlebars is a well-known templating library; usage here is consistent with workflow/validator functionality. | ai | |
| provenance | no-provenance | AI (provenance): Org-scoped package with clean history; lack of provenance is common and not a disqualifier here. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/resources | AI (phantom-deps): Declared in dependencies; OpenTelemetry packages often used via config/factory patterns. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/sdk-trace-base | AI (phantom-deps): Declared in dependencies; OpenTelemetry packages often used via config/factory patterns. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Declared in dependencies; used in config/schema-driven code paths, not a direct import pattern. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/exporter-trace-otlp-http | AI (phantom-deps): Declared in dependencies; OpenTelemetry packages often used via config/factory patterns. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/semantic-conventions | AI (phantom-deps): Declared in dependencies; OpenTelemetry packages often used via config/factory patterns. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): Declared in dependencies; likely used indirectly or in config-driven paths. | ai |
Versions (showing 51 of 54)
| Version | Deps | Published |
|---|---|---|
| 0.28.6 | 11 / 7 | |
| 0.28.5 | 11 / 7 | |
| 0.28.3 | 11 / 7 | |
| 0.28.0 | 11 / 7 | |
| 0.26.33 | 11 / 7 | |
| 0.26.31 | 11 / 7 | |
| 0.26.26 | 11 / 7 | |
| 0.26.24 | 11 / 7 | |
| 0.26.23 | 11 / 7 | |
| 0.26.22 | 11 / 7 | |
| 0.26.17 | 11 / 7 | |
| 0.26.16 | 11 / 7 | |
| 0.26.14 | 11 / 7 | |
| 0.26.13 | 11 / 7 | |
| 0.24.73 | 11 / 7 | |
| 0.24.38 | 11 / 7 | |
| 0.23.0 | 13 / 5 | |
| 0.10.0 | 13 / 5 | |
| 0.9.4 | 12 / 4 | |
| 0.9.3 | 11 / 4 | |
| 0.9.2 | 11 / 4 | |
| 0.9.1 | 11 / 4 | |
| 0.9.0 | 11 / 4 | |
| 0.8.0 | 10 / 4 | |
| 0.7.12 | 10 / 4 | |
| 0.7.11 | 10 / 4 | |
| 0.7.10 | 10 / 4 | |
| 0.7.9 | 10 / 4 | |
| 0.7.8 | 10 / 4 | |
| 0.7.7 | 10 / 4 | |
| 0.7.6 | 10 / 4 | |
| 0.7.5 | 10 / 4 | |
| 0.7.4 | 10 / 4 | |
| 0.7.3 | 10 / 4 | |
| 0.7.2 | 10 / 4 | |
| 0.7.1 | 10 / 4 | |
| 0.7.0 | 10 / 4 | |
| 0.6.4 | 10 / 4 | |
| 0.6.3 | 5 / 9 | |
| 0.6.2 | 5 / 9 | |
| 0.6.1 | 5 / 9 | |
| 0.6.0 | 5 / 9 | |
| 0.5.17 | 4 / 9 | |
| 0.5.16 | 4 / 9 | |
| 0.5.15 | 4 / 4 | |
| 0.5.14 | 4 / 4 | |
| 0.5.13 | 4 / 4 | |
| 0.5.12 | 4 / 4 | |
| 0.5.11 | 4 / 4 | |
| 0.5.10 | 4 / 4 | |
| 0.5.9 | 4 / 4 |
v0.24.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.