@qelos/plugin-play
Play a plugin for Qelos!
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used only in create-cert.js dev script, not in install or runtime path. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Standard JWT/auth header decoding pattern; no obfuscation or exfiltration. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads package.json from cwd for manifest metadata; stable benign pattern for this package. | ai | |
| phantom-deps | phantom-dep:@qelos/web-sdk | AI (phantom-deps): Same-org scoped package; declared as dep, phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@qelos/global-types | AI (phantom-deps): Same-org type-only dependency; not directly imported but used for type declarations. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 3.11.14 | 9 / 2 | |
| 3.11.13 | 9 / 2 | |
| 3.11.12 | 9 / 2 | |
| 3.11.11 | 9 / 2 | |
| 3.11.10 | 9 / 2 | |
| 3.11.9 | 9 / 2 | |
| 3.11.8 | 9 / 2 | |
| 3.11.7 | 9 / 2 | |
| 3.11.6 | 9 / 2 | |
| 3.11.5 | 9 / 2 | |
| 3.11.4 | 9 / 2 | |
| 3.11.3 | 9 / 2 | |
| 3.11.2 | 9 / 2 | |
| 3.11.1 | 9 / 2 | |
| 3.11.0 | 9 / 2 | |
| 3.10.0 | 9 / 2 | |
| 3.9.0 | 9 / 2 | |
| 3.8.3 | 8 / 2 |
v3.11.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.