@aws-amplify/data-schema
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 |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): 4.1x size increase explained by compiled output (tsbuildinfo, .js.map files); consistent with build refactor. | ai | |
| source-diff | obfuscated-file:dist/esm/ai/ConversationSchemaGraphQLTypes.d.ts | AI (source-diff): File is a TypeScript declaration exporting a GraphQL schema string constant, not obfuscated code. Normal pattern for schema distribution in AWS Amplify packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Common in AWS monorepo subpackages; not indicative of malice. | ai | |
| phantom-deps | phantom-dep:@types/aws-lambda | AI (phantom-deps): Framework-scoped type definitions loaded by convention in AWS packages. | ai | |
| phantom-deps | phantom-dep:@types/json-schema | AI (phantom-deps): Framework-scoped type definitions loaded by convention in schema packages. | ai | |
| dependencies | unvetted-dep:rxjs | AI (dependencies): rxjs is an established, widely-used reactive library; version constraint ^7.8.1 is reasonable and stable. | ai | |
| dependencies | unvetted-dep:@types/aws-lambda | AI (dependencies): Type definitions for AWS Lambda; framework-scoped dependency typical in AWS packages. | ai | |
| source-diff | large-new-source-files | AI (source-diff): 228 new files are compiled distribution artifacts and source maps, not injected code. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are established AWS/Smithy utilities; no suspicious patterns. | ai | |
| dependencies | unvetted-dep:@smithy/util-base64 | AI (dependencies): Smithy utility from AWS SDK; standard dependency for AWS service integration. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Addition of aws-amplify-data-runtime is consistent with AWS internal team organization; no takeover indicators present. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine maintainer rotation in large org; no concurrent new maintainers or takeover indicators. | ai | |
| provenance | no-provenance | AI (provenance): Provenance not yet standard for AWS Amplify releases; not a security indicator. | ai |
Versions (showing 19 of 119)
| Version | Deps | Published |
|---|---|---|
| 0.13.1 | 1 / 9 | |
| 0.13.0 | 1 / 9 | |
| 0.12.14 | 1 / 9 | |
| 0.12.13 | 1 / 9 | |
| 0.12.12 | 1 / 9 | |
| 0.12.11 | 1 / 9 | |
| 0.12.10 | 1 / 9 | |
| 0.12.9 | 1 / 9 | |
| 0.12.8 | 1 / 9 | |
| 0.12.7 | 1 / 9 | |
| 0.12.6 | 1 / 9 | |
| 0.12.5 | 1 / 9 | |
| 0.12.4 | 1 / 9 | |
| 0.12.3 | 1 / 9 | |
| 0.12.2 | 1 / 9 | |
| 0.12.1 | 1 / 9 | |
| 0.12.0 | 1 / 9 | |
| 0.11.1 | 1 / 9 | |
| 0.11.0 | 1 / 9 |
v0.13.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.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.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.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.