svelte-toolbelt
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Legit package's actual first version; publisher has strong track record. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Early scaffold version of a well-known, widely-used Svelte library. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 0.10.6 | 3 / 28 | |
| 0.10.5 | 3 / 28 | |
| 0.10.4 | 3 / 28 | |
| 0.10.3 | 3 / 28 | |
| 0.10.2 | 3 / 28 | |
| 0.10.1 | 3 / 28 | |
| 0.10.0 | 3 / 28 | |
| 0.9.3 | 3 / 28 | |
| 0.9.2 | 3 / 28 | |
| 0.9.1 | 3 / 28 | |
| 0.9.0 | 3 / 28 | |
| 0.8.2 | 3 / 28 | |
| 0.8.1 | 3 / 28 | |
| 0.8.0 | 3 / 28 | |
| 0.7.1 | 3 / 28 | |
| 0.7.0 | 3 / 28 | |
| 0.6.1 | 2 / 28 | |
| 0.6.0 | 2 / 28 | |
| 0.5.0 | 2 / 24 | |
| 0.4.6 | 2 / 24 | |
| 0.4.5 | 2 / 24 | |
| 0.4.4 | 2 / 24 | |
| 0.4.3 | 0 / 26 | |
| 0.4.2 | 2 / 24 | |
| 0.4.1 | 2 / 24 | |
| 0.4.0 | 2 / 24 | |
| 0.3.1 | 4 / 24 | |
| 0.3.0 | 4 / 24 | |
| 0.2.0 | 4 / 24 | |
| 0.1.0 | 0 / 23 | |
| 0.0.2 | 0 / 23 | |
| 0.0.1 | 0 / 23 | |
| 0.0.0 | 0 / 23 |
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.