@conduit-client/command-aura-graphql-normalized-cache-control
Luvio Aura GraphQL Normalized Cache Control Command
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@conduit-client/command-base | AI (phantom-deps): Monorepo internal re-export; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@conduit-client/command-aura-cache-control | AI (phantom-deps): Monorepo internal re-export; stable pattern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal library; minimal README and no-op main are expected for monorepo packages. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 3.21.0 | 12 / 0 | |
| 3.20.5 | 12 / 0 | |
| 3.20.4 | 12 / 0 | |
| 3.20.3 | 12 / 0 | |
| 3.20.0 | 12 / 0 | |
| 3.19.6 | 12 / 0 | |
| 3.19.5 | 12 / 0 | |
| 3.19.4 | 12 / 0 | |
| 3.19.3 | 12 / 0 | |
| 3.19.2 | 12 / 0 | |
| 3.19.1 | 12 / 0 | |
| 3.19.0 | 12 / 0 | |
| 3.18.0 | 12 / 0 | |
| 3.17.3 | 12 / 0 | |
| 3.17.2 | 12 / 0 | |
| 3.17.1 | 12 / 0 | |
| 3.17.0 | 12 / 0 | |
| 3.16.0 | 12 / 0 | |
| 3.15.1 | 12 / 0 | |
| 3.15.0 | 12 / 0 | |
| 3.14.0 | 12 / 0 | |
| 3.13.1 | 12 / 0 | |
| 3.13.0 | 12 / 0 | |
| 3.12.0 | 12 / 0 | |
| 3.11.0 | 12 / 0 | |
| 3.10.0 | 12 / 0 | |
| 3.9.0 | 12 / 0 | |
| 3.8.0 | 12 / 0 | |
| 3.7.1 | 12 / 0 | |
| 3.7.0 | 12 / 0 | |
| 3.6.3 | 12 / 0 | |
| 3.6.2 | 12 / 0 | |
| 3.6.1 | 12 / 0 | |
| 3.5.0 | 12 / 0 | |
| 3.4.0 | 12 / 0 | |
| 3.3.0 | 12 / 0 | |
| 3.2.0 | 12 / 0 | |
| 3.0.0 | 12 / 0 | |
| 2.1.0 | 12 / 0 | |
| 2.0.1 | 12 / 0 |
v3.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.