@diia-inhouse/types
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Framework-scoped package loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:@bufbuild/protobuf | AI (phantom-deps): Used in build/proto generation; legitimately declared and referenced. | ai | |
| phantom-deps | phantom-dep:type-fest | AI (phantom-deps): Utility types library; legitimately declared and used in type definitions. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 13.2.1 | 3 / 12 | |
| 13.2.0 | 3 / 12 | |
| 13.1.3 | 3 / 12 | |
| 13.1.2 | 3 / 12 | |
| 13.1.1 | 3 / 12 | |
| 13.1.0 | 3 / 12 | |
| 12.0.5 | 3 / 10 | |
| 12.0.4 | 3 / 10 | |
| 12.0.3 | 3 / 10 | |
| 12.0.2 | 3 / 10 | |
| 12.0.1 | 3 / 10 | |
| 12.0.0 | 3 / 10 | |
| 11.7.0 | 3 / 10 | |
| 11.6.0 | 3 / 10 | |
| 11.5.0 | 3 / 10 | |
| 11.4.2 | 3 / 10 | |
| 11.4.1 | 3 / 10 | |
| 11.4.0 | 3 / 10 | |
| 11.3.0 | 3 / 10 | |
| 10.0.11 | 3 / 10 | |
| 10.0.10 | 3 / 10 |
v13.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.