@flowgram.ai/i18n-plugin
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package; missing description is consistent across the @flowgram.ai/* namespace. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across the entire @flowgram.ai monorepo; not a per-version concern. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.0.11 | 2 / 14 | |
| 1.0.10 | 2 / 14 | |
| 1.0.9 | 2 / 14 | |
| 1.0.8 | 2 / 14 | |
| 1.0.7 | 2 / 14 | |
| 1.0.6 | 2 / 14 | |
| 1.0.3 | 2 / 14 | |
| 1.0.2 | 2 / 14 | |
| 1.0.1 | 2 / 14 | |
| 1.0.0 | 2 / 14 |
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.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.
v1.0.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.