@contrail/sdk
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:@nestjs/common | AI (phantom-deps): Likely used via TS types/decorators not caught by import scan; established dep. | ai | |
| provenance | publisher-changed | AI (provenance): Move to GitHub Actions CI publishing for this org's SDK; stable across future versions. | ai | |
| dependencies | unvetted-dep:@contrail/cache | AI (dependencies): First-party @contrail scoped sibling package, same publisher/monorepo. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are same-org first-party packages, not third-party additions. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are org colleagues; publisher matched known prior maintainer. | ai | |
| source-diff | obfuscated-file:docs/assets/main.js | AI (source-diff): Typedoc-generated docs bundle (lunr search), not injected obfuscation. | ai | |
| source-diff | obfuscated-file:docs/assets/search.js | AI (source-diff): Typedoc-generated search index/bundle, matches generate-docs script. | ai | |
| phantom-deps | phantom-dep:@contrail/util | AI (phantom-deps): Same-org dependency; likely used transitively or in config rather than direct import. | ai | |
| phantom-deps | phantom-dep:es6-promisify | AI (phantom-deps): Declared in package.json dependencies; likely used indirectly or in config files, stable false positive for this package. | ai |
Versions (showing 55 of 255)
| Version | Deps | Published |
|---|---|---|
| 1.0.59 | 2 / 8 | |
| 1.0.58 | 2 / 8 | |
| 1.0.57 | 2 / 8 | |
| 1.0.56 | 2 / 8 | |
| 1.0.55 | 2 / 8 | |
| 1.0.54 | 2 / 8 | |
| 1.0.53 | 2 / 8 | |
| 1.0.52 | 2 / 8 | |
| 1.0.51 | 2 / 8 | |
| 1.0.50 | 2 / 8 | |
| 1.0.49 | 2 / 8 | |
| 1.0.48 | 2 / 8 | |
| 1.0.47 | 2 / 8 | |
| 1.0.46 | 2 / 8 | |
| 1.0.45 | 2 / 8 | |
| 1.0.44 | 2 / 8 | |
| 1.0.43 | 2 / 8 | |
| 1.0.42 | 2 / 8 | |
| 1.0.41 | 3 / 7 | |
| 1.0.40 | 3 / 7 | |
| 1.0.39 | 3 / 7 | |
| 1.0.38 | 3 / 7 | |
| 1.0.37 | 3 / 7 | |
| 1.0.36 | 3 / 7 | |
| 1.0.34 | 3 / 7 | |
| 1.0.33 | 3 / 7 | |
| 1.0.32 | 3 / 7 | |
| 1.0.31 | 3 / 7 | |
| 1.0.30 | 3 / 7 | |
| 1.0.29 | 3 / 7 | |
| 1.0.28 | 2 / 7 | |
| 1.0.26 | 2 / 7 | |
| 1.0.25 | 2 / 7 | |
| 1.0.23 | 2 / 7 | |
| 1.0.22 | 2 / 7 | |
| 1.0.21 | 2 / 7 | |
| 1.0.20 | 2 / 7 | |
| 1.0.19 | 2 / 7 | |
| 1.0.18 | 1 / 7 | |
| 1.0.17 | 1 / 7 | |
| 1.0.16 | 1 / 7 | |
| 1.0.15 | 1 / 7 | |
| 1.0.14 | 1 / 7 | |
| 1.0.13 | 1 / 7 | |
| 1.0.12 | 1 / 7 | |
| 1.0.11 | 1 / 7 | |
| 1.0.10 | 1 / 7 | |
| 1.0.9 | 1 / 7 | |
| 1.0.8 | 1 / 7 | |
| 1.0.7 | 1 / 7 | |
| 1.0.6 | 1 / 7 | |
| 1.0.5 | 1 / 7 | |
| 1.0.2 | 1 / 7 | |
| 1.0.1 | 1 / 7 | |
| 1.0.0 | 1 / 7 |
v1.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.33
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 (brian.lindauer) than the most recent previously approved version (sharmaji_ag) on 2020-10-15, but brian.lindauer 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.32
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 (brian.lindauer) than the most recent previously approved version (sharmaji_ag) on 2020-10-01, but brian.lindauer 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.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
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 (brian.lindauer) than the most recent previously approved version (sharmaji_ag) on 2020-09-30, but brian.lindauer 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.29
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 (sharmaji_ag) than the most recent previously approved version (brian.lindauer) on 2020-09-30, but sharmaji_ag 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.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
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 (brian.lindauer) than the most recent previously approved version (sharmaji_ag) on 2020-09-17, but brian.lindauer 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.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
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 (sharmaji_ag) than the most recent previously approved version (brian.lindauer) on 2020-09-15, but sharmaji_ag 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.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
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. Consider requesting the maintainer enable provenance via CI/CD.
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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.