@node-projects/base-custom-webcomponent
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index-min.js | AI (source-diff): File is esbuild-minified bundle output per the explicit 'bundle' script in package.json; not malicious obfuscation. | ai | |
| source-diff | net-exec-file:dist/index-min.js | AI (source-diff): Minified bundle of webcomponent library; no actual network+exec dropper pattern in the code sample. | ai |
Versions (showing 84 of 84)
| Version | Deps | Published |
|---|---|---|
| 0.46.0 | 0 / 4 | |
| 0.45.0 | 0 / 4 | |
| 0.44.1 | 0 / 4 | |
| 0.44.0 | 0 / 4 | |
| 0.43.0 | 0 / 4 | |
| 0.42.0 | 0 / 4 | |
| 0.41.1 | 0 / 4 | |
| 0.41.0 | 0 / 4 | |
| 0.40.1 | 0 / 4 | |
| 0.40.0 | 0 / 4 | |
| 0.39.2 | 0 / 4 | |
| 0.39.1 | 0 / 4 | |
| 0.39.0 | 0 / 4 | |
| 0.38.0 | 0 / 4 | |
| 0.37.0 | 0 / 4 | |
| 0.36.0 | 0 / 4 | |
| 0.35.0 | 0 / 4 | |
| 0.34.0 | 0 / 3 | |
| 0.33.0 | 0 / 2 | |
| 0.32.0 | 0 / 2 | |
| 0.31.0 | 0 / 2 | |
| 0.30.0 | 0 / 2 | |
| 0.29.0 | 0 / 2 | |
| 0.28.2 | 0 / 2 | |
| 0.28.1 | 0 / 2 | |
| 0.28.0 | 0 / 2 | |
| 0.27.8 | 0 / 2 | |
| 0.27.7 | 0 / 2 | |
| 0.27.6 | 0 / 2 | |
| 0.27.5 | 0 / 2 | |
| 0.27.4 | 0 / 2 | |
| 0.27.3 | 0 / 2 | |
| 0.27.2 | 0 / 2 | |
| 0.27.1 | 0 / 2 | |
| 0.27.0 | 0 / 2 | |
| 0.26.1 | 0 / 2 | |
| 0.26.0 | 0 / 2 | |
| 0.25.10 | 0 / 2 | |
| 0.25.9 | 0 / 2 | |
| 0.25.8 | 0 / 2 | |
| 0.25.7 | 0 / 2 | |
| 0.25.6 | 0 / 2 | |
| 0.25.5 | 0 / 2 | |
| 0.25.4 | 0 / 2 | |
| 0.25.3 | 0 / 2 | |
| 0.25.2 | 0 / 2 | |
| 0.25.1 | 0 / 2 | |
| 0.25.0 | 0 / 2 | |
| 0.24.1 | 0 / 2 | |
| 0.24.0 | 0 / 1 | |
| 0.23.0 | 0 / 1 | |
| 0.22.0 | 0 / 1 | |
| 0.21.7 | 0 / 1 | |
| 0.21.5 | 0 / 1 | |
| 0.21.4 | 0 / 1 | |
| 0.21.3 | 0 / 1 | |
| 0.21.2 | 0 / 1 | |
| 0.21.1 | 0 / 1 | |
| 0.21.0 | 0 / 1 | |
| 0.20.0 | 0 / 1 | |
| 0.19.0 | 0 / 1 | |
| 0.18.1 | 0 / 1 | |
| 0.18.0 | 0 / 1 | |
| 0.17.2 | 0 / 1 | |
| 0.17.1 | 0 / 1 | |
| 0.17.0 | 0 / 1 | |
| 0.16.2 | 0 / 1 | |
| 0.16.1 | 0 / 1 | |
| 0.16.0 | 0 / 1 | |
| 0.15.0 | 0 / 1 | |
| 0.14.0 | 0 / 1 | |
| 0.13.0 | 0 / 1 | |
| 0.12.1 | 0 / 1 | |
| 0.12.0 | 0 / 1 | |
| 0.0.10 | 0 / 1 | |
| 0.0.9 | 0 / 1 | |
| 0.0.8 | 0 / 1 | |
| 0.0.7 | 0 / 1 | |
| 0.0.6 | 0 / 1 | |
| 0.0.5 | 0 / 1 | |
| 0.0.4 | 0 / 1 | |
| 0.0.3 | 0 / 1 | |
| 0.0.2 | 0 / 1 | |
| 0.0.1 | 0 / 1 |
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.