@accounter/green-invoice-graphql
Graphql proxy for Green Invoice API
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:path | AI (phantom-deps): Node built-in declared for bundler compat; stable FP. | ai | |
| phantom-deps | phantom-dep:graphql | AI (phantom-deps): Peer dep of graphql-mesh; resolved at runtime via mesh config. | ai | |
| phantom-deps | phantom-dep:@graphql-mesh/http | AI (phantom-deps): Mesh plugin loaded via config, not direct import; stable FP. | ai | |
| phantom-deps | phantom-dep:@graphql-mesh/store | AI (phantom-deps): Mesh plugin loaded via config; stable FP. | ai | |
| phantom-deps | phantom-dep:@graphql-mesh/types | AI (phantom-deps): Mesh types used at build time via config; stable FP. | ai | |
| phantom-deps | phantom-dep:@graphql-mesh/utils | AI (phantom-deps): Mesh utility loaded via config; stable FP. | ai | |
| phantom-deps | phantom-dep:@graphql-mesh/config | AI (phantom-deps): Mesh config loader; stable FP. | ai | |
| phantom-deps | phantom-dep:@graphql-mesh/runtime | AI (phantom-deps): Mesh runtime loaded via config; stable FP. | ai | |
| phantom-deps | phantom-dep:@graphql-mesh/json-schema | AI (phantom-deps): Mesh handler loaded via config; stable FP. | ai | |
| phantom-deps | phantom-dep:@graphql-mesh/cross-helpers | AI (phantom-deps): Mesh cross-helpers loaded via config; stable FP. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.8.4 | 10 / 0 | |
| 0.8.1 | 10 / 0 | |
| 0.8.0 | 10 / 0 | |
| 0.7.4 | 10 / 0 | |
| 0.6.0 | 10 / 5 |
v0.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.