@lightsparkdev/core
Lightspark JS SDK
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): Scoped Lightspark SDK package; name similarity to 'cors' is coincidental, not impersonation. | ai | |
| phantom-deps | phantom-dep:graphql | AI (phantom-deps): graphql is declared as a runtime dependency in package.json; phantom-dep heuristic misfires here. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.5.2 | 6 / 20 | |
| 1.5.1 | 6 / 20 | |
| 1.5.0 | 6 / 20 | |
| 1.4.9 | 6 / 20 | |
| 1.4.8 | 6 / 21 | |
| 1.4.7 | 6 / 21 | |
| 1.4.6 | 6 / 21 | |
| 1.4.5 | 6 / 21 | |
| 1.4.4 | 6 / 21 | |
| 1.4.3 | 6 / 20 | |
| 1.4.2 | 6 / 20 | |
| 1.4.1 | 6 / 20 | |
| 1.4.0 | 7 / 20 |
v1.5.2
2 findingsPackage name '@lightsparkdev/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.0
2 findingsPackage name '@lightsparkdev/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.9
2 findingsPackage name '@lightsparkdev/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.8
2 findingsPackage name '@lightsparkdev/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.
v1.4.7
2 findingsPackage name '@lightsparkdev/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.
v1.4.6
2 findingsPackage name '@lightsparkdev/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.
v1.4.5
2 findingsPackage name '@lightsparkdev/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.
v1.4.4
2 findingsPackage name '@lightsparkdev/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.
v1.4.3
2 findingsPackage name '@lightsparkdev/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.
v1.4.2
2 findingsPackage name '@lightsparkdev/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.
v1.4.1
2 findingsPackage name '@lightsparkdev/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.
v1.4.0
2 findingsPackage name '@lightsparkdev/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.