@flash-analytics/web
Enable `captureVariants` to automatically fetch variant assignments whenever a new session starts or a new profile is identified:
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Scoped analytics SDK with few metadata fields; not a spam/throwaway package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.1.9 | 1 / 4 | |
| 2.1.8 | 1 / 4 | |
| 2.1.7 | 1 / 4 | |
| 2.1.6 | 1 / 4 | |
| 2.1.0 | 1 / 4 | |
| 2.0.1 | 1 / 4 | |
| 1.0.9 | 1 / 4 | |
| 1.0.8 | 1 / 4 | |
| 1.0.7 | 1 / 4 |
v2.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: flash-analytics-10.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage 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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.