@itcase/common
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is explicitly listed in dependencies; phantom-dep is a false positive for this package. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 1.2.50 | 6 / 21 | |
| 1.2.49 | 6 / 21 | |
| 1.2.48 | 6 / 21 | |
| 1.2.47 | 6 / 21 | |
| 1.2.46 | 6 / 21 | |
| 1.2.45 | 6 / 21 | |
| 1.2.44 | 6 / 35 | |
| 1.2.43 | 6 / 35 | |
| 1.2.42 | 6 / 35 | |
| 1.2.41 | 6 / 35 | |
| 1.2.40 | 6 / 35 | |
| 1.2.39 | 6 / 35 | |
| 1.2.38 | 6 / 35 | |
| 1.2.37 | 6 / 36 | |
| 1.2.36 | 6 / 47 | |
| 1.2.35 | 6 / 47 | |
| 1.2.34 | 6 / 47 | |
| 1.2.33 | 6 / 47 | |
| 1.2.32 | 6 / 47 | |
| 1.2.31 | 6 / 47 | |
| 1.2.29 | 6 / 47 | |
| 1.2.28 | 6 / 47 | |
| 1.2.27 | 6 / 47 | |
| 1.2.26 | 5 / 46 | |
| 1.2.25 | 5 / 45 | |
| 1.2.24 | 5 / 44 | |
| 1.2.23 | 5 / 44 | |
| 1.2.22 | 5 / 44 | |
| 1.2.21 | 5 / 44 | |
| 1.2.20 | 5 / 44 | |
| 1.2.19 | 5 / 44 | |
| 1.2.18 | 5 / 44 | |
| 1.2.17 | 5 / 44 | |
| 1.2.16 | 5 / 44 | |
| 1.2.15 | 5 / 44 | |
| 1.2.13 | 5 / 44 | |
| 1.2.12 | 5 / 43 | |
| 1.2.11 | 5 / 43 | |
| 1.2.10 | 5 / 41 | |
| 1.2.9 | 5 / 41 | |
| 1.2.8 | 5 / 41 | |
| 1.2.7 | 5 / 41 | |
| 1.2.6 | 4 / 41 | |
| 1.2.5 | 4 / 37 | |
| 1.2.4 | 4 / 37 | |
| 1.2.3 | 4 / 37 | |
| 1.2.2 | 4 / 37 | |
| 1.2.1 | 4 / 37 |
v1.2.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.