bent
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:next | AI (typosquat): bent is a long-established HTTP client with no naming intent to impersonate 'next'. Edit distance of 2 is a false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): bent is a long-established HTTP client with no naming intent to impersonate 'jest'. Edit distance of 2 is a false positive for this package. | ai | |
| dependencies | unvetted-dep:bytesish | AI (dependencies): bytesish is authored by the same publisher (mikeal), making it a first-party dependency with low additional risk. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 7.3.12 | 3 / 5 | |
| 7.3.11 | 3 / 5 | |
| 7.3.10 | 3 / 5 | |
| 7.3.9 | 3 / 5 | |
| 7.3.8 | 3 / 5 | |
| 7.3.7 | 3 / 5 | |
| 7.3.6 | 3 / 5 | |
| 7.3.5 | 3 / 5 | |
| 7.3.4 | 3 / 5 | |
| 7.3.3 | 3 / 5 | |
| 7.3.2 | 3 / 5 | |
| 7.3.1 | 3 / 5 | |
| 7.3.0 | 3 / 5 | |
| 7.2.0 | 3 / 5 | |
| 7.1.2 | 3 / 5 | |
| 7.1.1 | 3 / 5 | |
| 7.1.0 | 3 / 5 | |
| 7.0.7 | 3 / 5 | |
| 7.0.6 | 3 / 5 | |
| 7.0.5 | 3 / 5 | |
| 7.0.4 | 3 / 5 | |
| 7.0.3 | 3 / 3 | |
| 7.0.2 | 3 / 3 | |
| 7.0.1 | 3 / 3 | |
| 7.0.0 | 3 / 3 |
v7.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.