@viamrobotics/svelte-sdk
Build Svelte apps with Viam
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): Intentional migration to GitHub Actions CI/CD publishing with SLSA provenance attestation; stable for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are viamrobotics org members; consistent with org-level ownership transition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of prior maintainer aligns with org-managed CI/CD publishing transition. | ai | |
| phantom-deps | phantom-dep:@tanstack/svelte-query-devtools | AI (phantom-deps): Listed as a runtime dependency in package.json; phantom-dep false positive for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.2.1 | 4 / 31 | |
| 1.2.0 | 4 / 31 | |
| 1.1.7 | 4 / 31 | |
| 1.1.6 | 4 / 31 | |
| 1.1.5 | 4 / 32 | |
| 1.1.4 | 4 / 32 | |
| 1.1.3 | 4 / 32 | |
| 1.1.2 | 4 / 32 | |
| 1.1.1 | 4 / 32 | |
| 1.1.0 | 4 / 32 | |
| 1.0.3 | 3 / 32 | |
| 1.0.1 | 3 / 32 | |
| 1.0.0 | 3 / 32 | |
| 0.7.3 | 1 / 34 | |
| 0.7.2 | 1 / 34 |
v1.1.5
2 findingsThis version was published by a different npm account than previous versions on 2026-03-25. 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.1.4
2 findingsThis version was published by a different npm account than previous versions on 2026-03-25. 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.1.3
2 findingsThis version was published by a different npm account than previous versions on 2026-03-17. 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.1.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-16. 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.1.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-16. 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.1.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-13. 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.0.3
2 findingsThis version was published by a different npm account than previous versions on 2026-01-22. 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.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.