@iyio/cdk-common
This library was generated with [Nx](https://nx.dev).
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@aws-cdk/aws-apigatewayv2-alpha | AI (dependencies): Alpha AWS CDK deps are expected for a CDK utility library; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@aws-cdk/aws-apigatewayv2-integrations-alpha | AI (dependencies): Alpha AWS CDK deps are expected for a CDK utility library; stable pattern across versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established CDK utility in iyio monorepo; missing metadata is a monorepo artifact, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): CDK/monorepo package; deps declared for peer/convention use, not direct import. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): CDK/monorepo package; deps declared for peer/convention use, not direct import. | ai | |
| phantom-deps | phantom-dep:node-fetch | AI (phantom-deps): CDK/monorepo package; deps declared for peer/convention use, not direct import. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/types | AI (phantom-deps): Framework-scoped AWS SDK type package; loaded by convention in CDK packages. | ai | |
| phantom-deps | phantom-dep:aws-jwt-verify | AI (phantom-deps): CDK/monorepo package; deps declared for peer/convention use, not direct import. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): CDK/monorepo package; deps declared for peer/convention use, not direct import. | ai | |
| phantom-deps | phantom-dep:@smithy/protocol-http | AI (phantom-deps): Framework-scoped Smithy package; loaded by convention in CDK packages. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/client-rds-data | AI (phantom-deps): Framework-scoped AWS SDK package; loaded by convention in CDK packages. | ai | |
| phantom-deps | phantom-dep:@aws-crypto/sha256-browser | AI (phantom-deps): CDK/monorepo package; deps declared for peer/convention use, not direct import. | ai | |
| phantom-deps | phantom-dep:amazon-cognito-identity-js | AI (phantom-deps): CDK/monorepo package; deps declared for peer/convention use, not direct import. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/credential-providers | AI (phantom-deps): Framework-scoped AWS SDK package; loaded by convention in CDK packages. | ai | |
| phantom-deps | phantom-dep:@smithy/signature-v4 | AI (phantom-deps): Framework-scoped Smithy package; loaded by convention in CDK packages. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): CDK/monorepo package; deps declared for peer/convention use, not direct import. | ai | |
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): CDK/monorepo package; deps declared for peer/convention use, not direct import. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.9.6 | 0 / 0 | |
| 0.9.1 | 0 / 0 | |
| 0.8.18 | 0 / 0 | |
| 0.8.17 | 0 / 0 | |
| 0.8.11 | 0 / 0 | |
| 0.8.1 | 0 / 0 | |
| 0.8.0 | 0 / 0 | |
| 0.7.43 | 17 / 0 | |
| 0.7.42 | 17 / 0 | |
| 0.7.37 | 17 / 0 | |
| 0.7.36 | 17 / 0 | |
| 0.7.34 | 17 / 0 | |
| 0.7.31 | 17 / 0 | |
| 0.7.29 | 17 / 0 | |
| 0.7.24 | 17 / 0 | |
| 0.7.23 | 18 / 0 | |
| 0.7.22 | 18 / 0 | |
| 0.7.19 | 18 / 0 | |
| 0.7.17 | 18 / 0 | |
| 0.7.15 | 18 / 0 | |
| 0.7.14 | 18 / 0 | |
| 0.7.13 | 18 / 0 |
v0.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.