@contrail/types
Types Utility module
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:jsurl | AI (phantom-deps): jsurl is declared in dependencies and likely used indirectly; phantom-dep heuristic fires but package is legitimate. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash declared in dependencies; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:node-fetch | AI (phantom-deps): node-fetch declared in dependencies; phantom-dep heuristic false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal scoped package (@contrail/*) consistently lacks public repo/keywords; metadata signals are stable false positives for this family. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 3.4.0 | 6 / 8 | |
| 3.3.0 | 6 / 8 | |
| 3.1.5 | 5 / 8 | |
| 3.1.4 | 5 / 8 | |
| 3.1.1 | 5 / 8 | |
| 3.1.0 | 5 / 8 | |
| 3.0.61 | 4 / 8 | |
| 3.0.60 | 4 / 8 | |
| 3.0.59 | 4 / 8 | |
| 3.0.58 | 4 / 8 | |
| 3.0.57 | 4 / 8 | |
| 3.0.56 | 4 / 8 | |
| 3.0.55 | 4 / 8 | |
| 3.0.54 | 4 / 8 | |
| 3.0.53 | 4 / 8 | |
| 3.0.52 | 4 / 8 | |
| 3.0.51 | 4 / 8 | |
| 3.0.50 | 4 / 8 | |
| 3.0.48 | 4 / 8 | |
| 3.0.47 | 4 / 8 | |
| 3.0.46 | 4 / 8 | |
| 3.0.45 | 4 / 8 | |
| 3.0.44 | 4 / 8 | |
| 3.0.43 | 4 / 8 |
v3.0.61
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (kamalvibeiq) than the most recent previously approved version (mattvitello) on 2024-04-08, but kamalvibeiq is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.60
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (kamalvibeiq) than the most recent previously approved version (mattvitello) on 2024-04-08, but kamalvibeiq is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.57
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mattvitello) than the most recent previously approved version (btosadoprater) on 2024-03-22, but mattvitello is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.56
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mattvitello) than the most recent previously approved version (btosadoprater) on 2024-03-20, but mattvitello is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.55
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (btosadoprater) than the most recent previously approved version (mattvitello) on 2024-02-23, but btosadoprater is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.53
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mattvitello) than the most recent previously approved version (kamalvibeiq) on 2024-02-19, but mattvitello is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.52
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (btosadoprater) than the most recent previously approved version (kamalvibeiq) on 2024-02-09, but btosadoprater is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.50
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (btosadoprater) than the most recent previously approved version (kamalvibeiq) on 2024-01-12, but btosadoprater is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.47
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (kamalvibeiq) than the most recent previously approved version (mattvitello) on 2023-11-29, but kamalvibeiq is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.46
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (kamalvibeiq) than the most recent previously approved version (mattvitello) on 2023-11-29, but kamalvibeiq is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.