@andrewcaires/node
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped utility package @andrewcaires/node; name similarity to zod is coincidental, not a typosquat. | ai | |
| phantom-deps | phantom-dep:tsx | AI (phantom-deps): tsx is a declared runtime dep used via the tsx-dev bin entry; not a phantom dependency. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 1.5.1 | 2 / 9 | |
| 1.5.0 | 2 / 9 | |
| 1.4.0 | 2 / 9 | |
| 1.3.3 | 2 / 9 | |
| 1.3.2 | 2 / 9 | |
| 1.3.1 | 2 / 9 | |
| 1.3.0 | 2 / 9 | |
| 1.2.10 | 2 / 9 | |
| 1.2.9 | 2 / 9 | |
| 1.2.8 | 2 / 9 | |
| 1.2.7 | 2 / 9 | |
| 1.2.6 | 2 / 9 | |
| 1.2.5 | 2 / 9 | |
| 1.2.4 | 2 / 9 | |
| 1.2.3 | 2 / 9 | |
| 1.2.2 | 2 / 9 | |
| 1.2.1 | 2 / 9 | |
| 1.2.0 | 2 / 9 | |
| 1.1.5 | 2 / 9 | |
| 1.1.4 | 2 / 9 | |
| 1.1.3 | 2 / 9 | |
| 1.1.2 | 2 / 10 | |
| 1.1.1 | 2 / 10 | |
| 1.1.0 | 2 / 10 | |
| 1.0.3 | 1 / 10 | |
| 1.0.2 | 1 / 10 | |
| 1.0.1 | 1 / 10 | |
| 1.0.0 | 1 / 10 |
v1.5.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.