@lightsparkdev/lightspark-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): Transition to GitHub Actions publishing confirmed by SLSA/Sigstore provenance attestation; stable for this package going forward. | ai | |
| source-diff | obfuscated-file:dist/index-DfbWBZ5s.d.cts | AI (source-diff): TypeScript declaration file generated by tsup bundler; long lines are normal for bundled .d.ts/.d.cts output. | ai | |
| source-diff | obfuscated-file:dist/index-J9dgrFWx.d.ts | AI (source-diff): TypeScript declaration file generated by tsup bundler; long lines are normal for bundled .d.ts output. | ai | |
| source-diff | obfuscated-file:dist/index-pcfnraJo.d.cts | AI (source-diff): Bundled TypeScript declaration file; long lines are tsup-generated type exports, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-C8aKLbL3.d.ts | AI (source-diff): Bundled TypeScript declaration file; long lines are tsup-generated type exports, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-tN3Kv2I2.d.cts | AI (source-diff): Bundled TypeScript declaration file; long lines are a tsup artifact, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-BZwvqXMx.d.ts | AI (source-diff): Bundled TypeScript declaration file; long lines are a tsup artifact, not obfuscation. | ai | |
| provenance | no-provenance | AI (provenance): Established org package; lack of provenance is consistent across all versions and not a risk indicator here. | ai | |
| phantom-deps | phantom-dep:graphql | AI (phantom-deps): graphql is a declared runtime dependency; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:dayjs | AI (phantom-deps): dayjs is a declared runtime dependency; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:zen-observable-ts | AI (phantom-deps): zen-observable-ts is a declared runtime dependency; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:graphql-ws | AI (phantom-deps): graphql-ws is a declared runtime dependency; phantom-dep heuristic false positive for this package. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decode used for HMAC webhook signature verification — standard cryptographic pattern, not payload execution. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): ws is a declared runtime dependency; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.9.19 | 8 / 20 | |
| 1.9.18 | 8 / 20 | |
| 1.9.17 | 8 / 20 | |
| 1.9.16 | 8 / 20 | |
| 1.9.15 | 8 / 20 | |
| 1.9.14 | 8 / 20 | |
| 1.9.13 | 8 / 20 | |
| 1.9.12 | 8 / 20 | |
| 1.9.11 | 8 / 20 | |
| 1.9.10 | 8 / 20 | |
| 1.9.9 | 8 / 20 | |
| 1.9.8 | 8 / 19 | |
| 1.9.7 | 8 / 19 | |
| 1.9.6 | 8 / 19 | |
| 1.9.5 | 8 / 19 | |
| 1.9.4 | 8 / 19 | |
| 1.9.3 | 8 / 19 | |
| 1.9.2 | 9 / 19 |
v1.9.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.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.
v1.9.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.14
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.13
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.12
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.11
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.10
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.