@oddbird/css-anchor-positioning
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/assets/polyfill-lc4Lm9c5.js | AI (source-diff): Vite-minified polyfill bundle, not obfuscation. | ai | |
| source-diff | net-exec-file:dist/assets/polyfill-lc4Lm9c5.js | AI (source-diff): modulepreload fetch of first-party assets; benign bundler runtime. | ai | |
| source-diff | obfuscated-file:dist/assets/main-D3wMyris.js | AI (source-diff): Minified demo bundle for the polyfill. | ai | |
| source-diff | obfuscated-file:dist/assets/polyfill-DVqHQ4vL.js | AI (source-diff): Minified Vite polyfill bundle; benign build artifact. | ai | |
| source-diff | obfuscated-file:dist/assets/main-DUDaQxzE.js | AI (source-diff): Minified Vite demo bundle, not obfuscation; matches build output. | ai | |
| source-diff | net-exec-file:dist/assets/polyfill-DVqHQ4vL.js | AI (source-diff): modulepreload fetch of link hrefs in build runtime; no code exec or exfil. | ai | |
| source-diff | obfuscated-file:dist/assets/polyfill-ZEo_y4cE.js | AI (source-diff): Vite-bundled polyfill asset; minification is expected for this build pipeline. | ai | |
| phantom-deps | phantom-dep:@types/css-tree | AI (phantom-deps): @types/css-tree is a type-only dependency used by TypeScript tooling, not a runtime import. | ai | |
| source-diff | net-exec-file:dist/assets/polyfill-ZEo_y4cE.js | AI (source-diff): fetch() calls are modulepreload polyfill boilerplate from Vite; no exfiltration or dropper pattern present. | ai | |
| source-diff | obfuscated-file:dist/assets/main-BIk8ZPG8.js | AI (source-diff): Vite-bundled demo asset; minification is expected for this build pipeline. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.9.0 | 4 / 31 | |
| 0.8.0 | 4 / 31 | |
| 0.7.0 | 4 / 31 | |
| 0.6.1 | 4 / 31 | |
| 0.6.0 | 4 / 31 | |
| 0.5.2 | 4 / 31 | |
| 0.5.1 | 4 / 31 | |
| 0.5.0 | 4 / 30 | |
| 0.4.0 | 4 / 29 | |
| 0.3.1 | 4 / 29 | |
| 0.3.0 | 4 / 29 | |
| 0.2.0 | 4 / 30 | |
| 0.1.1 | 4 / 30 | |
| 0.1.0 | 4 / 30 | |
| 0.0.5 | 4 / 30 | |
| 0.0.4 | 4 / 30 | |
| 0.0.3 | 4 / 31 | |
| 0.0.2 | 4 / 31 | |
| 0.0.1 | 3 / 26 |
v0.5.2
5 findingsThis version was published by a different npm account than previous versions on 2025-04-24. This could indicate a legitimate maintainer transition or an account compromise.
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.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
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 file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.