@aws/agent-inspector
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:react | AI (phantom-deps): React UI library; correctly declared and used in source. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): React UI library; correctly declared and used in source. | ai | |
| phantom-deps | phantom-dep:remark-gfm | AI (phantom-deps): Markdown plugin; correctly declared and used in source. | ai | |
| phantom-deps | phantom-dep:@ag-ui/core | AI (phantom-deps): UI component library; correctly declared and used in source. | ai | |
| phantom-deps | phantom-dep:lucide-react | AI (phantom-deps): Icon library; correctly declared and used in source. | ai | |
| phantom-deps | phantom-dep:react-markdown | AI (phantom-deps): Markdown renderer; correctly declared and used in source. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-react | AI (phantom-deps): ESLint plugin; correctly declared for linting config. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-import | AI (phantom-deps): ESLint plugin; correctly declared for linting config. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-prettier | AI (phantom-deps): ESLint plugin; correctly declared for linting config. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-react-hooks | AI (phantom-deps): ESLint plugin; correctly declared for linting config. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-testing-library | AI (phantom-deps): ESLint plugin; correctly declared for linting config. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.5.0 | 11 / 21 | |
| 0.4.2 | 11 / 21 | |
| 0.4.1 | 11 / 21 | |
| 0.4.0 | 11 / 21 | |
| 0.3.0 | 11 / 17 | |
| 0.2.1 | 11 / 17 | |
| 0.2.0 | 11 / 17 | |
| 0.1.0 | 11 / 17 |
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.