@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 36 of 36)
| 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 | |
| 0.1.1 | 11 / 14 | |
| 0.1.0 | 11 / 14 | |
| 0.0.64 | 11 / 14 | |
| 0.0.63 | 11 / 14 | |
| 0.0.62 | 11 / 14 | |
| 0.0.61 | 11 / 14 | |
| 0.0.60 | 11 / 14 | |
| 0.0.59 | 11 / 14 | |
| 0.0.58 | 11 / 14 | |
| 0.0.57 | 11 / 14 | |
| 0.0.56 | 11 / 14 | |
| 0.0.55 | 11 / 14 | |
| 0.0.54 | 11 / 14 | |
| 0.0.53 | 11 / 14 | |
| 0.0.52 | 11 / 14 | |
| 0.0.51 | 11 / 14 | |
| 0.0.50 | 11 / 14 | |
| 0.0.49 | 11 / 14 |
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.64
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This 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.
v0.0.63
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This 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.
v0.0.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.