@lightsparkdev/lightspark-cli
CLI for the Lightspark JS sdk
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher is GitHub Actions with SLSA provenance attestation; CI/CD publishing is the documented release process for this org. | ai | |
| provenance | no-provenance | AI (provenance): Established Lightspark org package; missing provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): Listed in dependencies; phantom-dep heuristic false positive for this CLI package. | ai | |
| phantom-deps | phantom-dep:jose | AI (phantom-deps): Listed in dependencies and used by CLI; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lightsparkdev/core | AI (phantom-deps): Same-org dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:jsonwebtoken | AI (phantom-deps): Listed in dependencies; phantom-dep heuristic false positive for this CLI package. | ai | |
| phantom-deps | phantom-dep:dayjs | AI (phantom-deps): Listed in dependencies; phantom-dep heuristic false positive for this CLI package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.1.19 | 11 / 14 | |
| 0.1.18 | 11 / 14 | |
| 0.1.17 | 11 / 14 | |
| 0.1.16 | 11 / 13 | |
| 0.1.15 | 11 / 14 | |
| 0.1.14 | 11 / 14 | |
| 0.1.13 | 11 / 14 | |
| 0.1.12 | 11 / 14 | |
| 0.1.11 | 11 / 14 | |
| 0.1.10 | 11 / 14 | |
| 0.1.9 | 11 / 14 | |
| 0.1.8 | 11 / 14 | |
| 0.1.7 | 11 / 14 | |
| 0.1.6 | 11 / 14 | |
| 0.1.5 | 11 / 14 | |
| 0.1.4 | 11 / 14 | |
| 0.1.3 | 11 / 14 | |
| 0.1.2 | 11 / 14 |
v0.1.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.18
2 findingsThis version was published by a different npm account than previous versions on 2026-03-27. 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.1.17
2 findingsThis version was published by a different npm account than previous versions on 2026-03-06. 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.1.16
2 findingsThis version was published by a different npm account than previous versions on 2026-02-10. 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.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.