@quiltt/core
Javascript API client and utilities for Quiltt
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-ruby-client | AI (phantom-deps): graphql-ruby-client is a declared runtime dep; phantom-dep heuristic fires on config-only references, stable false positive. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped SDK package @quiltt/core; name similarity to cors is coincidental, not impersonation. | ai | |
| phantom-deps | phantom-dep:braces | AI (phantom-deps): braces is declared as a runtime dep; phantom-dep heuristic misfires here. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 6.0.1 | 6 / 7 | |
| 6.0.0 | 6 / 7 | |
| 5.3.0 | 6 / 7 | |
| 5.2.5 | 6 / 7 | |
| 5.2.4 | 6 / 7 | |
| 5.2.3 | 6 / 7 | |
| 5.2.2 | 6 / 7 | |
| 5.2.0 | 6 / 7 | |
| 5.1.3 | 6 / 7 | |
| 5.1.2 | 6 / 7 | |
| 5.1.1 | 6 / 7 | |
| 5.1.0 | 6 / 7 | |
| 5.0.3 | 6 / 7 | |
| 5.0.2 | 6 / 7 | |
| 5.0.1 | 6 / 7 | |
| 5.0.0 | 6 / 7 | |
| 4.5.1 | 6 / 7 | |
| 4.5.0 | 6 / 7 | |
| 4.4.0 | 6 / 7 |
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.5
2 findingsPackage name '@quiltt/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.4
2 findingsPackage name '@quiltt/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.3
2 findingsPackage name '@quiltt/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.2
2 findingsPackage name '@quiltt/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
2 findingsPackage name '@quiltt/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.3
2 findingsPackage name '@quiltt/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.2
2 findingsPackage name '@quiltt/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
2 findingsPackage name '@quiltt/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
2 findingsPackage name '@quiltt/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
2 findingsPackage name '@quiltt/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
2 findingsPackage name '@quiltt/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
2 findingsPackage name '@quiltt/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
2 findingsPackage name '@quiltt/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.1
2 findingsPackage name '@quiltt/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.0
2 findingsPackage name '@quiltt/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
2 findingsPackage name '@quiltt/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.