@sweefi/sui
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Manual publish variance, no malicious behavior evident; consistent with small team workflow. | ai | |
| dependencies | unvetted-peer-dep:@sweefi/server | AI (dependencies): Internal monorepo sibling package, optional peer dep. | ai | |
| dependencies | unvetted-dep:@sweefi/server | AI (dependencies): Sibling workspace package from same monorepo/publisher, not third-party. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Internal workspace dependency addition, benign monorepo pattern. | ai | |
| provenance | no-provenance | AI (provenance): Small ecosystem package; no provenance is common and not a disqualifier here. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): @sweefi/sui is a Sui blockchain SDK, not a typosquat of uuid; scoped name makes impersonation implausible. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @sweefi/sui is a Sui blockchain SDK, not a typosquat of joi; scoped name makes impersonation implausible. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): @sweefi/sui is a Sui blockchain SDK, not a typosquat of yup; scoped name makes impersonation implausible. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.4.2 | 3 / 9 | |
| 0.4.1 | 3 / 9 | |
| 0.4.0 | 3 / 9 | |
| 0.3.0 | 3 / 9 | |
| 0.2.2 | 3 / 9 | |
| 0.2.1 | 2 / 9 | |
| 0.2.0 | 2 / 9 |
v0.3.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dannydevs.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dannydevs.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.