@contrail/org-config-migration
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher moved to GitHub Actions CI within same scope; no payload change. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with CI-publish handoff on this scoped package; no malicious change. | ai | |
| dependencies | unvetted-dep:json2csv | AI (dependencies): json2csv is a legitimate, widely-used CSV library; alpha version constraint is a minor quality concern, not a security risk. | ai | |
| provenance | no-provenance | AI (provenance): Established @contrail scoped package; no provenance is common and not a risk signal here. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.2.0 | 5 / 10 | |
| 1.1.13 | 5 / 10 | |
| 1.1.12 | 5 / 10 | |
| 1.1.11 | 5 / 10 | |
| 1.1.10 | 5 / 10 | |
| 1.1.9 | 5 / 10 | |
| 1.1.8 | 5 / 10 | |
| 1.1.7 | 5 / 10 | |
| 1.1.6 | 5 / 10 | |
| 1.1.5 | 5 / 10 | |
| 1.1.4 | 5 / 10 | |
| 1.1.3 | 5 / 10 | |
| 1.1.2 | 5 / 10 | |
| 1.1.1 | 5 / 10 | |
| 1.1.0 | 5 / 10 | |
| 1.0.3 | 3 / 10 | |
| 1.0.2 | 3 / 10 | |
| 1.0.1 | 3 / 10 |
v1.2.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-19. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ashutoshvibeiq) than the most recent previously approved version (prashantvibeiq) on 2025-10-15, but ashutoshvibeiq 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.5
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (prashantvibeiq) than the most recent previously approved version (rakeshvibeiq) on 2025-10-10, but prashantvibeiq 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.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rakeshvibeiq) than the most recent previously approved version (kamalvibeiq) on 2025-04-30, but rakeshvibeiq 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.0
2 findingsThis version was published by a different npm account (kamalvibeiq) than the most recent previously approved version (rakeshvibeiq) on 2025-04-03. It has since remained available on npm for 470 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
2 findingsThis version was published by a different npm account (rakeshvibeiq) than the most recent previously approved version (kamalvibeiq) on 2024-06-27. It has since remained available on npm for 751 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.