@zeedhi/core
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @zeedhi/core package with 197 versions and 2681-day history; not a typosquat of cors. | ai |
Versions (showing 78 of 78)
| Version | Deps | Published |
|---|---|---|
| 3.0.5 | 10 / 5 | |
| 1.131.0 | 9 / 6 | |
| 1.130.0 | 9 / 6 | |
| 1.129.1 | 9 / 6 | |
| 1.129.0 | 9 / 6 | |
| 1.128.0 | 9 / 6 | |
| 1.127.0 | 9 / 6 | |
| 1.126.0 | 9 / 6 | |
| 1.125.0 | 9 / 6 | |
| 1.124.0 | 9 / 6 | |
| 1.123.0 | 9 / 6 | |
| 1.122.0 | 9 / 6 | |
| 1.121.0 | 9 / 6 | |
| 1.120.5 | 9 / 6 | |
| 1.120.4 | 9 / 6 | |
| 1.120.3 | 9 / 6 | |
| 1.120.2 | 9 / 6 | |
| 1.120.1 | 9 / 6 | |
| 1.120.0 | 9 / 6 | |
| 1.119.0 | 9 / 6 | |
| 1.118.0 | 9 / 6 | |
| 1.117.0 | 9 / 6 | |
| 1.116.0 | 9 / 6 | |
| 1.115.0 | 9 / 6 | |
| 1.114.0 | 9 / 6 | |
| 1.113.0 | 9 / 6 | |
| 1.112.0 | 9 / 6 | |
| 1.111.1 | 9 / 6 | |
| 1.111.0 | 9 / 6 | |
| 1.110.1 | 9 / 6 | |
| 1.110.0 | 9 / 6 | |
| 1.109.1 | 9 / 6 | |
| 1.109.0 | 9 / 6 | |
| 1.108.1 | 9 / 6 | |
| 1.108.0 | 9 / 6 | |
| 1.107.3 | 9 / 6 | |
| 1.107.1 | 9 / 6 | |
| 1.107.0 | 9 / 6 | |
| 1.106.1 | 9 / 6 | |
| 1.106.0 | 9 / 6 | |
| 1.105.1 | 9 / 6 | |
| 1.105.0 | 9 / 6 | |
| 1.104.0 | 9 / 6 | |
| 1.103.2 | 9 / 6 | |
| 1.103.1 | 9 / 6 | |
| 1.103.0 | 9 / 6 | |
| 1.102.0 | 9 / 6 | |
| 1.101.1 | 9 / 6 | |
| 1.101.0 | 9 / 6 | |
| 1.100.1 | 9 / 6 | |
| 1.100.0 | 9 / 6 | |
| 1.99.0 | 9 / 6 | |
| 1.98.1 | 9 / 6 | |
| 1.98.0 | 9 / 6 | |
| 1.97.6 | 9 / 6 | |
| 1.97.5 | 9 / 6 | |
| 1.97.4 | 9 / 6 | |
| 1.97.3 | 9 / 6 | |
| 1.97.2 | 9 / 6 | |
| 1.97.1 | 9 / 6 | |
| 1.97.0 | 9 / 6 | |
| 1.96.3 | 9 / 6 | |
| 1.96.2 | 9 / 6 | |
| 1.96.1 | 9 / 6 | |
| 1.96.0 | 9 / 6 | |
| 1.95.1 | 9 / 6 | |
| 1.94.3 | 9 / 6 | |
| 1.94.2 | 9 / 6 | |
| 1.94.1 | 9 / 6 | |
| 1.94.0 | 9 / 6 | |
| 1.93.2 | 9 / 6 | |
| 1.93.1 | 9 / 6 | |
| 1.93.0 | 9 / 6 | |
| 1.92.1 | 9 / 6 | |
| 1.92.0 | 9 / 6 | |
| 1.91.3 | 9 / 6 | |
| 1.91.2 | 9 / 6 | |
| 1.91.1 | 9 / 6 |
v1.131.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.107.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.106.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.106.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.105.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.105.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.104.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.103.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.103.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.103.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.102.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.101.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.101.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.100.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.100.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.99.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.98.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.98.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.97.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.97.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.97.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.97.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.97.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.97.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.96.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.96.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.96.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.96.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.95.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.92.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.92.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.91.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.91.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.91.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.