smob
Zero dependency library to safe merge objects.
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:glob | AI (typosquat): smob is a safe-merge-objects library; the name is intentional and unrelated to 'glob'. Levenshtein proximity is coincidental. | ai | |
| typosquat | typosquat.levenshtein:mobx | AI (typosquat): smob is a safe-merge-objects library; the name is intentional and unrelated to 'mobx'. Levenshtein proximity is coincidental. | ai | |
| provenance | no-provenance | AI (provenance): Lack of Sigstore provenance is common (~88% of npm packages); no other risk signals present to elevate this concern. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.6.2 | 0 / 10 | |
| 1.6.1 | 0 / 14 | |
| 1.6.0 | 0 / 14 | |
| 1.5.0 | 0 / 16 | |
| 1.4.1 | 0 / 16 | |
| 1.4.0 | 0 / 16 | |
| 1.3.0 | 0 / 16 | |
| 1.2.0 | 0 / 17 | |
| 1.1.1 | 0 / 17 | |
| 1.1.0 | 0 / 17 | |
| 1.0.0 | 0 / 18 |
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.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.