@dwtechs/checkard
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 |
|---|---|---|---|---|
| email-domain | unclaimed-email:http://www.lcluber.com/contact | AI (email-domain): Author used a URL as the email field; lcluber.com is the author's real site, not an unclaimed domain. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 3.6.1 | 0 / 12 | |
| 3.6.0 | 0 / 12 | |
| 3.5.1 | 0 / 12 | |
| 3.5.0 | 0 / 12 | |
| 3.4.1 | 0 / 12 | |
| 3.4.0 | 0 / 12 | |
| 3.3.0 | 0 / 12 | |
| 3.2.3 | 0 / 10 | |
| 3.2.2 | 0 / 10 | |
| 3.2.1 | 0 / 10 | |
| 3.2.0 | 0 / 10 | |
| 3.1.0 | 0 / 10 | |
| 3.0.0 | 0 / 10 |
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.