← Home

@donmahallem/rollup-config

My Rollup config. Use at your own risk!

100
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

donmahallem

Versions (showing 100 of 183)

Version Deps Published
4.2.38 7 / 20
4.2.37 7 / 20
4.2.36 7 / 20
4.2.35 7 / 20
4.2.34 7 / 20
4.2.33 7 / 20
4.2.32 7 / 20
4.2.31 7 / 20
4.2.30 7 / 20
4.2.29 7 / 20
4.2.28 7 / 20
4.2.27 7 / 20
4.2.26 7 / 20
4.2.25 7 / 20
4.2.24 7 / 20
4.2.23 7 / 20
4.2.22 7 / 20
4.2.21 7 / 20
4.2.20 7 / 20
4.2.19 7 / 20
4.2.18 7 / 20
4.2.17 7 / 20
4.2.16 7 / 20
4.2.15 7 / 20
4.2.14 7 / 20
4.2.13 7 / 20
4.2.12 7 / 20
4.2.11 7 / 20
4.2.10 7 / 20
4.2.9 7 / 20
4.2.8 7 / 20
4.2.7 7 / 20
4.2.6 7 / 20
4.2.5 7 / 20
4.2.4 7 / 20
4.2.3 7 / 20
4.2.2 7 / 20
4.2.1 7 / 20
4.2.0 7 / 20
4.1.141 7 / 19
4.1.140 7 / 19
4.1.139 7 / 19
4.1.138 7 / 19
4.1.137 7 / 19
4.1.136 7 / 19
4.1.135 7 / 19
4.1.134 7 / 19
4.1.133 7 / 19
4.1.132 7 / 19
4.1.131 7 / 19
4.1.130 7 / 19
4.1.129 7 / 19
4.1.128 7 / 19
4.1.127 7 / 19
4.1.126 7 / 19
4.1.125 7 / 19
4.1.124 7 / 19
4.1.123 7 / 19
4.1.122 7 / 19
4.1.121 7 / 19
4.1.120 7 / 19
4.1.119 7 / 19
4.1.118 7 / 19
4.1.117 7 / 19
4.1.116 7 / 19
4.1.115 7 / 19
4.1.114 7 / 19
4.1.113 7 / 19
4.1.112 7 / 19
4.1.111 7 / 19
4.1.110 7 / 19
4.1.109 7 / 19
4.1.108 7 / 19
4.1.107 7 / 19
4.1.106 7 / 19
4.1.105 7 / 19
4.1.104 7 / 19
4.1.103 7 / 19
4.1.102 7 / 19
4.1.101 7 / 19
4.1.100 7 / 19
4.1.99 7 / 19
4.1.98 7 / 19
4.1.97 7 / 19
4.1.96 7 / 19
4.1.95 7 / 19
4.1.94 7 / 19
4.1.93 7 / 19
4.1.92 7 / 19
4.1.91 7 / 19
4.1.90 7 / 19
4.1.89 7 / 19
4.1.88 7 / 19
4.1.87 7 / 19
4.1.86 7 / 19
4.1.85 7 / 19
4.1.84 7 / 19
4.1.83 7 / 19
4.1.82 7 / 19
4.1.81 7 / 19
Showing 100 of 183 Next page →

v4.2.38

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v4.2.37

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v4.2.36

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v4.2.35

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v4.2.34

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v4.1.108

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.107

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.106

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.105

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.104

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.103

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.102

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.101

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.100

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.99

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.98

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.97

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.96

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.95

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.94

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.93

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.92

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.91

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.90

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.89

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.88

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.87

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.86

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.85

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.84

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.83

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.82

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.1.81

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.