← Home

apollo-angular

Use your GraphQL data in your Angular app, with the Apollo Client

3
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

urigopowerkikikamilkisielatheguild-bot

Keywords

apollographqlangularschematicsangular-schematics

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Migrated to GitHub Actions CI/CD with SLSA provenance; legitimate for this org. ai
provenance missing-githead AI (provenance): Expected when publishing via GitHub Actions CI/CD instead of npm CLI directly. ai
publish-pattern dormant-publish AI (publish-pattern): Major version bump (v14) after stable v13; normal for Angular ecosystem packages. ai

Versions (showing 3 of 3)

Version Deps Published
14.0.0 1 / 0
13.0.0 1 / 0
7.0.2 1 / 0

v14.0.0

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

HIGH Publisher changed: powerkiki → GitHub Actions (on 2026-05-13) provenance

This version was published by a different npm account than previous versions on 2026-05-13. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v7.0.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.