@dwtechs/winstan
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): Email field contains a contact URL, not an email address; domain-hijack risk is not applicable here. | ai | |
| typosquat | typosquat.levenshtein:winston | AI (typosquat): Package is an intentional winston wrapper; name similarity is by design, not impersonation. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.7.1 | 1 / 8 | |
| 0.7.0 | 1 / 8 | |
| 0.6.0 | 1 / 5 | |
| 0.5.0 | 1 / 5 | |
| 0.4.0 | 2 / 5 | |
| 0.3.0 | 2 / 6 | |
| 0.2.1 | 2 / 7 | |
| 0.2.0 | 2 / 7 | |
| 0.1.1 | 2 / 6 | |
| 0.1.0 | 2 / 6 |
v0.7.1
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.1
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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.