@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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): New publisher has strong track record (42/0) across many packages; no malicious diff. | ai | |
| phantom-deps | phantom-dep:crypto-browserify | AI (phantom-deps): Used via browser field config, not direct import; benign. | ai | |
| 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 25 of 25)
| 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 | |
| 1.3.1 | 7 / 20 | |
| 1.3.0 | 7 / 19 | |
| 1.2.8 | 7 / 18 | |
| 1.2.7 | 7 / 18 | |
| 1.2.6 | 7 / 18 | |
| 1.2.5 | 7 / 18 | |
| 1.2.4 | 7 / 18 | |
| 1.2.3 | 8 / 19 | |
| 1.2.2 | 8 / 19 | |
| 1.2.1 | 8 / 19 | |
| 1.2.0 | 8 / 19 | |
| 1.1.0 | 8 / 19 |
v1.3.1
2 findingsThis version was published by a different npm account than previous versions on 2025-04-04. 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.
v1.3.0
2 findingsThis version was published by a different npm account than previous versions on 2025-03-16. 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.
v1.2.8
2 findingsThis version was published by a different npm account than previous versions on 2025-02-20. 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.
v1.2.7
2 findingsThis version was published by a different npm account than previous versions on 2025-02-05. 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.
v1.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.