@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 |
|---|---|---|---|---|
| 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 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 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.22.3 | 5 / 5 | |
| 0.22.2 | 5 / 5 | |
| 0.22.1 | 5 / 5 | |
| 0.22.0 | 4 / 5 | |
| 0.20.0 | 4 / 5 | |
| 0.19.0 | 4 / 5 | |
| 0.18.0 | 4 / 5 |
v1.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.22.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.