@llumiverse/core
Provide an universal API to LLMs. Support for existing LLMs can be added by writing a driver.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): aregnier-vertesia is a known maintainer with 75 approved packages; transition appears legitimate. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP is 127.0.0.1 in a test file — localhost test server setup, not malicious. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Buffer.from with base64 is standard embeddings byte conversion, not obfuscation. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Established LLM library under @llumiverse scope; name similarity to 'cors' is coincidental, not impersonation. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is a type-only dev/runtime dep; not directly imported by convention. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 1.4.1 | 6 / 4 | |
| 1.4.0 | 6 / 4 | |
| 1.3.0 | 5 / 5 | |
| 1.2.0 | 5 / 5 | |
| 1.1.0 | 5 / 5 | |
| 1.0.0 | 5 / 5 | |
| 0.25.1 | 5 / 5 | |
| 0.25.0 | 5 / 5 | |
| 0.24.0 | 5 / 5 | |
| 0.23.0 | 5 / 5 | |
| 0.22.3 | 5 / 5 | |
| 0.22.2 | 5 / 5 | |
| 0.22.1 | 5 / 5 | |
| 0.22.0 | 4 / 5 | |
| 0.21.0 | 4 / 5 | |
| 0.20.0 | 4 / 5 | |
| 0.19.0 | 4 / 5 | |
| 0.18.0 | 4 / 5 | |
| 0.17.0 | 3 / 5 | |
| 0.16.0 | 3 / 7 | |
| 0.15.0 | 3 / 7 | |
| 0.14.0 | 3 / 7 | |
| 0.13.0 | 1 / 7 | |
| 0.10.0 | 1 / 6 | |
| 0.9.2 | 1 / 6 | |
| 0.9.1 | 1 / 6 | |
| 0.9.0 | 1 / 6 | |
| 0.8.4 | 1 / 5 | |
| 0.8.3 | 1 / 5 | |
| 0.8.1 | 1 / 5 | |
| 0.8.0 | 1 / 5 |
v1.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-05. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (bstefanescu) than the most recent previously approved version (mincong-vertesia) on 2025-12-15, but bstefanescu is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.21.0
2 findingsThis version was published by a different npm account than previous versions on 2025-07-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.