swell-js
Swell JS library for client-side stores
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Long-lived package with 194 versions; dormancy followed by a clean patch release with no material changes is low risk. | ai | |
| dependencies | unvetted-dep:fast-case | AI (dependencies): fast-case is a stable, well-known camelCase utility; long-standing dep in this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 5.6.1 | 3 / 55 | |
| 5.6.0 | 3 / 55 | |
| 5.5.1 | 3 / 55 | |
| 5.5.0 | 3 / 55 | |
| 5.4.1 | 3 / 55 | |
| 5.4.0 | 3 / 55 | |
| 5.3.0 | 3 / 55 | |
| 5.2.0 | 3 / 55 | |
| 5.1.3 | 3 / 54 | |
| 5.1.2 | 3 / 54 | |
| 5.1.1 | 3 / 54 | |
| 5.1.0 | 3 / 53 | |
| 5.0.0 | 3 / 52 |
v5.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.