← Home

@holoscript/graphql-api

GraphQL API layer for HoloScript compiler with TypeGraphQL and Apollo Server

3
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

brianonbased

Keywords

holoscriptgraphqlapollotype-graphqlcompiler-api

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:jsonwebtoken AI (phantom-deps): Likely imported transitively or via dynamic require in auth middleware; stable for this package. ai
phantom-deps phantom-dep:@envelop/core AI (phantom-deps): Envelop plugin system uses indirect imports; stable false positive. ai
phantom-deps phantom-dep:graphql-shield AI (phantom-deps): Used via type-graphql/envelop plugin wiring; stable false positive. ai
phantom-deps phantom-dep:express-rate-limit AI (phantom-deps): Middleware registered dynamically on Express; stable false positive. ai
phantom-deps phantom-dep:graphql-rate-limit AI (phantom-deps): GraphQL directive-based usage; stable false positive. ai
phantom-deps phantom-dep:@envelop/response-cache AI (phantom-deps): Envelop plugin registered at runtime; stable false positive. ai

Versions (showing 3 of 3)

Version Deps Published
0.1.2 20 / 7
0.1.1 20 / 7
0.1.0 20 / 7

v0.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.