@quatrain/core
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:module-alias | AI (phantom-deps): module-alias is used via _moduleAliases config in package.json, not direct import; stable false positive. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @quatrain/core is an established package (102 versions, SLSA provenance); no relation to the cors package. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() used for typed property access in ORM-style TypeScript code; not obfuscation. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 1.2.17 | 4 / 10 | |
| 1.2.16 | 4 / 10 | |
| 1.2.15 | 4 / 10 | |
| 1.2.13 | 4 / 10 | |
| 1.2.2 | 3 / 11 | |
| 1.1.52 | 3 / 11 | |
| 1.1.49 | 5 / 11 | |
| 1.1.48 | 5 / 11 | |
| 1.1.47 | 5 / 11 | |
| 1.1.46 | 5 / 11 | |
| 1.1.45 | 5 / 11 | |
| 1.1.44 | 5 / 11 | |
| 1.1.43 | 5 / 11 | |
| 1.1.42 | 5 / 11 | |
| 1.1.38 | 5 / 11 | |
| 1.1.37 | 5 / 11 | |
| 1.1.36 | 5 / 11 | |
| 1.1.35 | 5 / 11 | |
| 1.1.34 | 5 / 11 | |
| 1.1.33 | 5 / 11 | |
| 1.1.32 | 5 / 11 | |
| 1.1.31 | 5 / 11 | |
| 1.1.30 | 5 / 11 | |
| 1.1.29 | 5 / 11 | |
| 1.1.28 | 5 / 11 | |
| 1.1.19 | 4 / 10 | |
| 1.1.18 | 4 / 10 | |
| 1.1.17 | 4 / 10 | |
| 1.1.16 | 4 / 10 | |
| 1.1.15 | 4 / 10 | |
| 1.1.14 | 3 / 10 | |
| 1.1.13 | 3 / 10 | |
| 1.1.12 | 3 / 10 | |
| 1.1.11 | 3 / 10 | |
| 1.1.10 | 3 / 10 | |
| 1.1.9 | 3 / 10 | |
| 1.1.8 | 3 / 10 | |
| 1.1.7 | 3 / 10 | |
| 1.1.6 | 3 / 10 | |
| 1.1.4 | 2 / 9 | |
| 1.1.3 | 2 / 9 | |
| 1.1.2 | 2 / 9 | |
| 1.1.1 | 2 / 9 | |
| 1.1.0 | 2 / 9 | |
| 1.0.3 | 2 / 9 | |
| 1.0.2 | 2 / 9 | |
| 1.0.1 | 2 / 9 | |
| 1.0.0 | 2 / 9 |
v1.2.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.13
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: crapougnax.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.