@oscarpalmer/mora
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:koa | AI (typosquat): Scoped package under author's own namespace; not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:mobx | AI (typosquat): Scoped package under author's own namespace; not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:mocha | AI (typosquat): Scoped package under author's own namespace; not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package under author's own namespace; not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:morgan | AI (typosquat): Scoped package under author's own namespace; not a typosquat. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() in a proxy helper is standard pattern for reactive/signal libraries; not obfuscation. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 0.29.0 | 1 / 9 | |
| 0.28.0 | 1 / 8 | |
| 0.27.0 | 1 / 8 | |
| 0.26.0 | 1 / 10 | |
| 0.25.0 | 1 / 10 | |
| 0.24.0 | 1 / 11 | |
| 0.23.0 | 1 / 12 | |
| 0.22.0 | 1 / 13 | |
| 0.21.0 | 1 / 12 | |
| 0.20.0 | 1 / 12 | |
| 0.19.0 | 1 / 12 | |
| 0.18.2 | 1 / 12 | |
| 0.18.1 | 1 / 12 | |
| 0.18.0 | 1 / 12 | |
| 0.17.0 | 1 / 12 | |
| 0.16.0 | 1 / 12 | |
| 0.15.0 | 1 / 12 | |
| 0.14.0 | 1 / 12 | |
| 0.13.0 | 1 / 12 | |
| 0.12.0 | 1 / 12 | |
| 0.11.1 | 1 / 12 | |
| 0.11.0 | 1 / 12 | |
| 0.10.0 | 1 / 12 | |
| 0.9.0 | 1 / 12 | |
| 0.8.0 | 0 / 13 | |
| 0.7.0 | 0 / 13 | |
| 0.6.0 | 0 / 13 | |
| 0.5.0 | 0 / 13 | |
| 0.4.0 | 0 / 13 | |
| 0.3.0 | 0 / 13 | |
| 0.2.0 | 0 / 13 | |
| 0.1.0 | 0 / 12 |
v0.4.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.