cssconflict

$ cat demo/white.css
x {
    color: white;
}
$ cat demo/black.css
x {
    color: black;
    display: inline-block;
}
$ cssconflict demo/white.css demo/black.css
x {
  color: white; /* demo/white.css */
  color: black; /* demo/black.css */
}

Metadata

Release files for cssconflict 0.1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for cssconflict 0.1.2
File	Size	Uploaded	Provenance	Actions
cssconflict-0.1.2.tar.gz	2.4 kB	Mar 4, 2016	Without provenance	Details for cssconflict-0.1.2.tar.gz

Release files / cssconflict-0.1.2.tar.gz

Download URL	cssconflict-0.1.2.tar.gz
Size	2.4 kB
Tags	Source
SHA-256 checksum How to use checksums	`8f2d37ac8a421f9d183f25f5f339bd9cfd60822ee4bf2fca3c6f989154736e32`
BLAKE2b-256 checksum How to use checksums	`4d4e81e792efe273fb8711646700779a2068fd5db7bde87d192cf8a48cf740f2`
Upload date	Mar 4, 2016
Uploaded using Trusted Publishing? What is trusted publishing?	No

Security for cssconflict 0.1.2

Report project as malware

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

cssconflict 0.1.2

cssconflict

Project links

Key dates

1 maintainer

Credits

License

Tags

Classifiers