@factorialco/agent-chat
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:remark-gfm | AI (phantom-deps): Declared dependency used in markdown processing; stable for this package. | ai | |
| phantom-deps | phantom-dep:react-markdown | AI (phantom-deps): Declared dependency used in markdown rendering; stable for this package. | ai | |
| phantom-deps | phantom-dep:tailwind-merge | AI (phantom-deps): Declared dependency used in styling; stable for this package. | ai | |
| phantom-deps | phantom-dep:@tabler/icons-react | AI (phantom-deps): Declared dependency used in icon rendering; stable for this package. | ai | |
| phantom-deps | phantom-dep:react-syntax-highlighter | AI (phantom-deps): Declared dependency used in code highlighting; stable for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.5.0 | 7 / 18 | |
| 1.4.1 | 7 / 18 | |
| 1.4.0 | 7 / 18 | |
| 1.3.3 | 7 / 17 | |
| 1.3.2 | 7 / 17 | |
| 1.3.1 | 7 / 17 | |
| 1.3.0 | 7 / 17 | |
| 1.2.1 | 7 / 17 | |
| 1.2.0 | 7 / 17 | |
| 1.1.0 | 7 / 17 | |
| 1.0.0 | 7 / 17 | |
| 0.3.5 | 7 / 17 |
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.