@allstak/js
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped SDK package for AllStak platform; name similarity to 'qs' is coincidental, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped SDK package; no relation to jest. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped SDK package; no relation to pg. | ai | |
| typosquat | typosquat.levenshtein:rxjs | AI (typosquat): Scoped SDK package; no relation to rxjs. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped SDK package; no relation to joi. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped SDK package; no relation to ajv. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.2.3 | 0 / 11 | |
| 0.2.2 | 0 / 11 | |
| 0.2.1 | 0 / 11 | |
| 0.2.0 | 0 / 11 | |
| 0.1.3 | 0 / 11 | |
| 0.1.2 | 0 / 11 | |
| 0.1.1 | 0 / 11 |
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
2 findingsPackage name '@allstak/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.