@forwardimpact/svcgraph
Graph query service for Guide
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Internal org package; no provenance is consistent across all versions in this suite. | ai | |
| phantom-deps | phantom-dep:n3 | AI (phantom-deps): n3 is declared as a runtime dep; phantom-dep heuristic may miss indirect/dynamic usage in this ESM service. | ai | |
| phantom-deps | phantom-dep:@forwardimpact/libresource | AI (phantom-deps): Same-org dep; phantom-dep heuristic commonly misfires on intra-org scoped packages. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.1.73 | 8 / 1 | |
| 0.1.72 | 8 / 1 | |
| 0.1.71 | 7 / 1 | |
| 0.1.70 | 6 / 1 | |
| 0.1.69 | 5 / 1 | |
| 0.1.68 | 5 / 1 | |
| 0.1.67 | 5 / 1 | |
| 0.1.66 | 5 / 1 | |
| 0.1.65 | 5 / 1 | |
| 0.1.64 | 5 / 1 | |
| 0.1.63 | 5 / 1 | |
| 0.1.62 | 5 / 1 | |
| 0.1.61 | 5 / 1 | |
| 0.1.60 | 5 / 1 | |
| 0.1.58 | 5 / 1 | |
| 0.1.57 | 5 / 1 | |
| 0.1.56 | 5 / 1 |
v0.1.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.