@-xun/project-graph
The project analysis utilities available to consumers of the @-xun/project package
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:find-up~5 | AI (dependencies): Aliased npm dep pattern for pinning find-up v5 alongside newer major; legitimate versioning technique, not a supply-chain risk. | ai | |
| dependencies | unvetted-dep:escape-string-regexp~4 | AI (dependencies): Same aliased dep pattern for escape-string-regexp v4; well-known utility package, no risk. | ai | |
| phantom-deps | phantom-dep:@types/semver | AI (phantom-deps): @types/semver is a type-only dep used at compile time; not imported at runtime by convention. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.2.4 | 20 / 3 | |
| 3.2.3 | 20 / 3 | |
| 3.2.2 | 20 / 3 | |
| 3.2.1 | 20 / 3 | |
| 3.2.0 | 20 / 3 | |
| 3.1.0 | 20 / 3 | |
| 3.0.0 | 20 / 3 |
v3.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.