@macrostrat/data-sheet
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/node/data-sheet.dffdda71.js | AI (source-diff): Parcel build output; minified but readable imports of known deps matching package purpose. | ai | |
| source-diff | obfuscated-file:dist/node/data-sheet.2a613259.js | AI (source-diff): Parcel build output; minified but readable imports of known deps matching package purpose. | ai | |
| source-diff | obfuscated-file:dist/node/data-sheet.6a663031.js | AI (source-diff): Parcel build output; minified but readable imports of known deps matching package purpose. | ai | |
| source-diff | obfuscated-file:dist/node/data-sheet.f3404ed5.js | AI (source-diff): Parcel bundler minified output; readable imports confirm legitimate React/Blueprint code. | ai | |
| phantom-deps | phantom-dep:chroma-js | AI (phantom-deps): Declared dep used transitively via bundled dist; phantom-dep heuristic fires on bundled packages. | ai | |
| phantom-deps | phantom-dep:react-color | AI (phantom-deps): Same bundled-dist false positive pattern. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): Same bundled-dist false positive pattern. | ai | |
| source-diff | obfuscated-file:dist/node/data-sheet.4a8fd8a7.js | AI (source-diff): Parcel bundler minified output; readable imports confirm legitimate React/Blueprint code. | ai | |
| source-diff | obfuscated-file:dist/node/data-sheet.d40ac2ae.js | AI (source-diff): Parcel bundler minified output; readable imports confirm legitimate React/Blueprint code. | ai | |
| provenance | no-provenance | AI (provenance): Established @macrostrat monorepo package; no provenance is consistent across all versions. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 14 / 1 | |
| 3.0.4 | 13 / 1 | |
| 3.0.3 | 13 / 1 | |
| 3.0.2 | 13 / 1 | |
| 3.0.1 | 15 / 1 | |
| 3.0.0 | 15 / 1 | |
| 2.2.4 | 15 / 2 | |
| 2.2.3 | 16 / 2 | |
| 2.2.2 | 16 / 2 | |
| 2.2.1 | 16 / 2 |
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.3
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.