@glodon-aiot/dataset-annotation
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): Consistent across all versions of this org-scoped package; not a malware indicator. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal scoped component library; missing metadata is consistent across all 315 versions, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:react-redux | AI (phantom-deps): Redux packages often loaded via store config, not direct import; stable false positive for this UI component package. | ai | |
| phantom-deps | phantom-dep:@types/fabric | AI (phantom-deps): Type-only package; not directly imported in source, loaded by convention. | ai | |
| phantom-deps | phantom-dep:@reduxjs/toolkit | AI (phantom-deps): Toolkit loaded via store config, not direct import; stable false positive. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.17.0 | 19 / 48 | |
| 3.16.0 | 19 / 48 | |
| 3.9.1 | 19 / 48 | |
| 3.8.0 | 19 / 48 | |
| 3.6.2 | 19 / 48 |
v3.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.