@qvac/rag
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:bare-fetch | AI (phantom-deps): Used via package.json imports conditional exports for Bare runtime, not a direct import. | ai | |
| phantom-deps | phantom-dep:bare-crypto | AI (phantom-deps): Used via package.json imports conditional exports for Bare runtime, not a direct import. | ai | |
| phantom-deps | phantom-dep:crypto-browserify | AI (phantom-deps): Used via package.json imports conditional exports as a browser/default shim, not a direct import. | ai | |
| phantom-deps | phantom-dep:hyperdht | AI (phantom-deps): hyperdht is a declared runtime dependency; phantom-dep heuristic misfires here. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @qvac/rag is a RAG library unrelated to the postgres 'pg' package; Levenshtein match is coincidental. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.6.2 | 10 / 9 | |
| 0.6.1 | 10 / 9 | |
| 0.6.0 | 10 / 9 | |
| 0.5.0 | 3 / 12 | |
| 0.4.4 | 5 / 12 | |
| 0.4.3 | 6 / 12 | |
| 0.4.2 | 6 / 12 | |
| 0.4.1 | 6 / 12 | |
| 0.2.2 | 6 / 11 | |
| 0.2.1 | 5 / 11 | |
| 0.2.0 | 5 / 11 | |
| 0.1.1 | 5 / 11 | |
| 0.1.0 | 5 / 11 |
v0.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.