@contrail/transform-data
Libraries for transforming data
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:node-fetch | AI (phantom-deps): node-fetch is a runtime dependency; phantom-dep heuristic fires on config-only references. | ai | |
| phantom-deps | phantom-dep:@contrail/sdk | AI (phantom-deps): Same-org scoped dependency; phantom-dep heuristic is overly broad for org-internal packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Metadata-only signals (no README code blocks, no repo URL); established package with 34 versions and ecosystem trust. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.3.0 | 4 / 14 | |
| 1.2.0 | 4 / 14 | |
| 1.1.4 | 4 / 14 | |
| 1.1.3 | 4 / 14 | |
| 1.1.2 | 4 / 14 | |
| 1.1.1 | 4 / 14 | |
| 1.0.15 | 4 / 14 | |
| 1.0.14 | 4 / 14 | |
| 1.0.13 | 4 / 14 | |
| 1.0.12 | 4 / 14 | |
| 1.0.11 | 4 / 14 | |
| 1.0.10 | 4 / 14 | |
| 1.0.9 | 4 / 14 | |
| 1.0.8 | 4 / 14 | |
| 1.0.7 | 4 / 14 | |
| 1.0.6 | 4 / 14 |
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
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 (chris_vibeiq) on 2024-10-15, 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.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
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 (chris_vibeiq) on 2023-07-02, 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.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.