@accounter/hashavshevet-mesh
Graphql proxy for Hashavshevet 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:@graphql-mesh/http | AI (phantom-deps): Mesh plugin loaded via config; stable pattern. | ai | |
| phantom-deps | phantom-dep:@graphql-mesh/store | AI (phantom-deps): Mesh plugin loaded via config; stable pattern. | ai | |
| phantom-deps | phantom-dep:@graphql-mesh/types | AI (phantom-deps): Mesh plugin loaded via config; stable pattern. | ai | |
| phantom-deps | phantom-dep:@graphql-mesh/utils | AI (phantom-deps): Mesh plugin loaded via config; stable pattern. | ai | |
| phantom-deps | phantom-dep:@graphql-mesh/config | AI (phantom-deps): Mesh plugin loaded via config; stable pattern. | ai | |
| phantom-deps | phantom-dep:@graphql-mesh/runtime | AI (phantom-deps): Mesh plugin loaded via config; stable pattern. | ai | |
| phantom-deps | phantom-dep:graphql | AI (phantom-deps): Runtime dep consumed via GraphQL Mesh config, not direct import; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@graphql-mesh/json-schema | AI (phantom-deps): Mesh plugin loaded via config; stable pattern. | ai | |
| phantom-deps | phantom-dep:@graphql-mesh/cross-helpers | AI (phantom-deps): Mesh plugin loaded via config; stable pattern. | ai | |
| phantom-deps | phantom-dep:@graphql-mesh/transform-resolvers-composition | AI (phantom-deps): Mesh plugin loaded via config; stable pattern. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.2.10 | 10 / 0 | |
| 0.2.7 | 10 / 0 | |
| 0.2.6 | 10 / 0 | |
| 0.2.5 | 10 / 0 | |
| 0.2.0 | 10 / 4 |
v0.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.