@types/n3
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:pg | AI (typosquat): @types/n3 is a DefinitelyTyped scoped package for the n3 RDF library; Levenshtein proximity to 'pg' is coincidental and not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @types/n3 is a DefinitelyTyped scoped package for the n3 RDF library; Levenshtein proximity to 'qs' is coincidental and not a typosquat. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is a framework-scoped type package loaded by convention in TypeScript projects; not directly imported in type definition packages. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 1.26.1 | 2 / 0 | |
| 1.26.0 | 2 / 0 | |
| 1.25.3 | 2 / 0 | |
| 1.25.2 | 2 / 0 | |
| 1.25.1 | 2 / 0 | |
| 1.25.0 | 2 / 0 | |
| 1.24.3 | 2 / 0 | |
| 1.24.2 | 2 / 0 | |
| 1.24.1 | 2 / 0 | |
| 1.24.0 | 2 / 0 | |
| 1.21.1 | 2 / 0 | |
| 1.21.0 | 2 / 0 | |
| 1.20.0 | 2 / 0 | |
| 1.16.5 | 2 / 0 | |
| 1.16.4 | 2 / 0 | |
| 1.16.3 | 2 / 0 | |
| 1.16.2 | 2 / 0 | |
| 1.16.1 | 2 / 0 | |
| 1.16.0 | 2 / 0 | |
| 1.10.4 | 2 / 0 | |
| 1.10.3 | 2 / 0 | |
| 1.10.2 | 2 / 0 | |
| 1.10.1 | 2 / 0 | |
| 1.10.0 | 2 / 0 |
v1.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.