@sylphx/sdk
Sylphx SDK - State-of-the-art platform SDK with pure functions
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:jose | AI (phantom-deps): Listed as runtime dependency; likely imported in bundled dist entry points not statically traced by the heuristic. | ai | |
| phantom-deps | phantom-dep:rrweb | AI (phantom-deps): Listed as runtime dependency for web-analytics entry; bundled output not statically traced. | ai | |
| phantom-deps | phantom-dep:web-vitals | AI (phantom-deps): Listed as runtime dependency for web-analytics entry; bundled output not statically traced. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 0.16.0 | 4 / 10 | |
| 0.15.4 | 4 / 10 | |
| 0.15.3 | 4 / 10 | |
| 0.15.2 | 4 / 10 | |
| 0.15.1 | 4 / 10 | |
| 0.15.0 | 4 / 10 | |
| 0.14.0 | 4 / 10 | |
| 0.13.9 | 4 / 10 | |
| 0.13.8 | 4 / 10 | |
| 0.13.0 | 4 / 10 | |
| 0.12.2 | 4 / 10 | |
| 0.12.1 | 4 / 10 | |
| 0.12.0 | 4 / 10 | |
| 0.11.2 | 4 / 10 | |
| 0.11.1 | 4 / 10 | |
| 0.11.0 | 4 / 10 | |
| 0.10.7 | 4 / 10 | |
| 0.10.6 | 4 / 10 | |
| 0.10.5 | 4 / 10 | |
| 0.10.4 | 4 / 10 | |
| 0.10.3 | 4 / 10 | |
| 0.10.2 | 4 / 10 | |
| 0.10.1 | 4 / 10 | |
| 0.10.0 | 4 / 10 | |
| 0.9.0 | 4 / 10 | |
| 0.8.0 | 4 / 10 | |
| 0.7.0 | 4 / 10 | |
| 0.5.0 | 4 / 11 |
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.